You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hub/apps/design/shell/tiles-and-notifications/push-request-response-headers.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -315,6 +315,7 @@ Each HTTP message contains one of these response codes. WNS recommends that deve
315
315
| 405 Method Not Allowed | Invalid method (GET, CREATE); only POST (Windows or Windows Phone) or DELETE (Windows Phone only) is allowed. | Log the details of your request. Switch to using HTTP POST. |
316
316
| 406 Not Acceptable | The cloud service exceeded its throttle limit. | Please send your request after the Retry-After header value in the response |
317
317
| 410 Gone | The channel expired. | Log the details of your request. Do not send further notifications to this channel. Have your app request a new channel URI. |
318
+
| 410 Domain Blocked | The sending domain has been blocked by WNS. | Do not send further notifications to this channel. The sending domain has been blocked by WNS for abusing push notifications. |
318
319
| 413 Request Entity Too Large | The notification payload exceeds the 5000 byte size limit. | Log the details of your request. Inspect the payload to ensure it is within the size limitations. |
319
320
| 500 Internal Server Error | An internal failure caused notification delivery to fail. | Log the details of your request. Report this issue through the developer forums. |
320
321
| 503 Service Unavailable | The server is currently unavailable. | Log the details of your request. Report this issue through the developer forums. If the Retry-After header is observed then please send your request after the Retry-After header value in the response. |
0 commit comments