mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #737] UTF-8 Actions Header #538
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#538
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cfouche3005 on GitHub (May 20, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/737
🐞 Describe the bug
Ntfy server seem to block every POST request with an UTF-8 character ( à ) inside the Actions Header (for the label) but when I had an an UTF-8 character inside the Title Header or the body, it is processed normally and give the correct output or an unknow character due to bad UTF-8 processing (not a bug, I think)
💻 Components impacted
Ntfy Server
💡 Screenshots and/or logs
ntfy server log:
Actions Header :
http, "Mettre à jour", "https://REDACTED/webhook/netbird-update", method=GET, headers.AUTH=REDACTED🔮 Additional context
I can't use the JSON method because I need the Icon parameter and it isn't supported
@binwiederhier commented on GitHub (May 21, 2023):
UTF-8 headers are supported by the ntfy server, but many clients have trouble with it. So it is likely that your IDE and/or programming language is incorrectly encoding the header. This is because the HTTP spec doesn't officially support UTF-8 header.
It works on Linux with curl:
That said, a few of the other headers can already be encoded with RFC 2047 type strings, but the action description cannot. Maybe we should add that support too. Then you could do:
I think that's reasonable.
The icon param should be supported. Here's and example with curl:
@cfouche3005 commented on GitHub (May 21, 2023):
Yes, It would be very nice.
It was not inside the overview of the supported field of the documentation so I thought it was not supported
https://docs.ntfy.sh/publish/#publish-as-json
@binwiederhier commented on GitHub (May 22, 2023):
Done in
github.com/binwiederhier/ntfy@168ad8bf1b-- Will be in the next release