Windows Push Notification service (WNS) returns the wrong status code for rate limiting

[collimarco]

Describe the bug

From your docs:

406 Not Acceptable
The cloud service exceeded its throttle limit.
Please send your request after the Retry-After header value in the response

This is plain wrong and against the standard. You MUST return 429 Too Many Requests for rate limiting.

Returning 406 breaks various web push libraries and services, that don't handle the response properly.

For example: zaru/webpush#103

Steps to reproduce the bug

Send many web push messages in parallel to Edge / WNS.

Expected behavior

Return HTTP status 429 for rate limiting.

Screenshots

No response

NuGet package version

None

Windows version

No response

Additional context

No response

[collimarco]

Any updates on this issue?

[jan-krueger]

As far as I can tell, they are currently responding with a 429 based on the responses I have seen so far. Maybe they have switched and the documentation is just outdated?