Exception Webpush Requests Too Large
I went through the logs on the Server and mentioned some Exceptions that are not handled by the application.
Please discuss, if it makes sense to log this Exception and sent it to sentry or if it is better to capture it in the application
Please also write if you know the cause of the Exception.
Summary
There are many failures in Webpush requests here are only a few caused by a too large request. I think a too large request should not happen.
What is the current bug behavior?
Webpush Messages are too large
What is the expected correct behavior?
Size of the Messages should be checked before sending to web push service
Relevant error messages and/or screenshots
Message failed to send for subscription https://updates.push.services.mozilla.com/wpush/v1/xxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxx: Client error: `POST https://updates.push.services.mozilla.com/wpush/v1/xxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxx` resulted in a `413 Request Entity Too Large` response:
{"code": 413, "errno": 104, "error": "Payload Too Large", "more_info": "http://autopush.readthedocs.io/en/latest/http.ht (truncated...)
Count: 2341
Possible fixes
Add a size Check before sending request to the Server
Edited by Stefan C