Catching endpoint errors?

[web-push-libs]

Catching endpoint errors?

[Minishlink]

Hi, this is a great question! Some time ago, push servers were not responding with any handful content when a failure occured. Now, they do (at least Chrome). You can look at the content of this response (cf. #25).

That being said, it would be great to have a dev-friendly flag that notices whether you have to invalidate the endpoint in your database. I'll look if the error codes have been standardized.

[Minishlink]

In the spec, the server must answer with a 404 if a subscription is expired. But Firefox has answered with 410 for me... You can now check the "expired" key in the results array, on master.

[amardeokar23]

I get 400 on chrome if i use endpoint which is not subscribed or wrong endpoint.

HTTP/1.1 400 UnauthorizedRegistration

Can we use expired flag for this ?

[amardeokar23]

Also, can we return endpoint along with expired flag so that we will exactly know which endpoint to remove.