Re: [w3c/push-api] Add a messageHandlingError event (#214)

If this is a decryption problem, that's either a programming error or a DoS attack.  You are suggesting that we compound the DoS by waking the application as well as the browser.

What other reasons are there for a message arriving for a subscription that isn't going to be delivered?

Note that most browsers log decryption failures to developer consoles, so a developer can debug their code that way.

-- 
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/issues/214#issuecomment-257764394