- From: Martin Thomson <notifications@github.com>
- Date: Wed, 08 Jun 2016 18:37:09 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc:
Received on Thursday, 9 June 2016 01:37:53 UTC
There is no good way to recover from decryption failure, so the browser might as well acknowledge them. That will prevent the push service from sending them again, which is good. The main drawback is that it looks to the application server like they were successful. This came up in discussions at the IETF. You can view, comment on, or merge this pull request online at: https://github.com/w3c/push-api/pull/195 -- Commit Summary -- * Acknowledge messages that fail to decrypt -- File Changes -- M index.html (19) -- Patch Links -- https://github.com/w3c/push-api/pull/195.patch https://github.com/w3c/push-api/pull/195.diff --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/195
Received on Thursday, 9 June 2016 01:37:53 UTC