We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudflare apparently adds a Priority: u=... header to requests, which ntfy rejects with 500 invalid priority (should be a 400). This is a new HTTP standard (https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-priority) that is emerging.
Priority: u=...
500 invalid priority
We should ignore header values that start with u=. It is quite unfortunate that the name conflicts like this.
u=
The text was updated successfully, but these errors were encountered:
Fixed in 95bd876
Sorry, something went wrong.
This ticket (#353) has a full dump of the Cloudflare request showing the Priority: u=3 header.
Priority: u=3
No branches or pull requests
Cloudflare apparently adds a
Priority: u=...
header to requests, which ntfy rejects with500 invalid priority
(should be a 400). This is a new HTTP standard (https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-priority) that is emerging.We should ignore header values that start with
u=
. It is quite unfortunate that the name conflicts like this.The text was updated successfully, but these errors were encountered: