Bad Gateway 502 about web-push-csharp HOT 3 CLOSED

5000 HTTP Post requests should not be a problem for the HttpClient; No matter if you call it synchronously or asynchronously. However I am not an expert on this topic.

As far as I understood, it is up to the push server (browser manufactorer) to reject push notifications, for example to filter spam, and the more "un-spam-like" your notification behaviour is, the more likely is that they get delivered.

Web push notifications should be

Timely, Relevant, and Precise (https://developers.google.com/web/fundamentals/push-notifications/)

in other words, it should be a short information targetted to a specific user, and it should reach the user in the right moment. Therefore also no broadcast capability is included in the standard.

Recently, I discussed the following case: A specific feature of a platform was under maintainance for some hours. The request was to inform all the users of the platform via web push that the feature is back online.
I suggested to provide a method for the user to request the notification instead of informing all the users. Like when a user tries to use an unavailable feature, some text explains that its currently under maintainance next to a button "inform me when available".
This has the advantage that other users don't feel "spammed", while the user who's waiting for the functionality is informed in the right moment, that its up again. A side effect is that users who didn't try to access the platform during that time did not even notice that it was unavailable.

from web-push-csharp.

502 bad gateway:
The server was acting as a gateway or proxy and received an invalid response from the upstream server.

As far as I can tell this would imply a temporary outage of the providers end. If a bad request was sent or you were being rate limited, i would expect a different response code (400, 429).

from web-push-csharp.

Thanks for the insight!
Today I got a 406 error code from edge / windows push notification service. The code doc says:

The cloud service exceeded its throttle limit. Log the details of your request. Reduce the rate at which you are sending notifications.

Does anyone know which rate is acceptable for edge?

EDIT: otherwise you can close this "issue". thanks for the help!

from web-push-csharp.