Skip to content

Conversation

jrconlin
Copy link
Member

@jrconlin jrconlin commented Mar 4, 2024

Description

Microsoft has introduced extra
header
requirements for incoming push messages. I kind of want to avoid adding a lot of system specific smarts to pywebpush, mostly because that's an endless road of feature creep. The preferred way to handle this would be to include the extra, call specific headers in the webpush(..., headers=dict(...)) argument.

Some users have reported issues with the non-standard WebPush headers that Microsoft requires. I've added guidance for them in the README. In addition, Google has long announced the end of support for FCM tokens. Might as well drop them now.

Issue(s)

Closes #162

jrconlin added 2 commits March 4, 2024 09:52
Microsoft has introduced [extra
header](https://learn.microsoft.com/en-us/windows/apps/design/shell/tiles-and-notifications/push-request-response-headers#request-parameters)
requirements for incoming push messages. I kind of want to avoid adding
a lot of system specific smarts to pywebpush, mostly because that's an
endless road of feature creep. The preferred way to handle this would be
to include the extra, call specific headers in the `webpush(...,
headers=dict(...))` argument.

Closes #162
@jrconlin jrconlin changed the title feat: Add --wns option to handle WNS header feat: Add WNS comment, drop GCM/FCM direct support Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

400 Bad Request when using Windows Push Notification Services (WNS) endpoint

1 participant