mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1617] Header X-Tags is not honored #1134
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#1134
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 @caronc on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1617
🐞 Describe the bug
Ntfy documentation identifies the use of setting
X-Tagswhich does not appear to work. However settingtagsin the JSON payload does work.Would advise to either support
X-Tagsas documented or just drop it from documentation since the payload method works fine too. All otherX-Header-Optionsappear to be correctly honored.note: I did not test
Tagson it's own.Apprise workaround in place works fine using tags in payload
💻 Components impacted
all
💡 Screenshots and/or logs
n/a
🔮 Additional context
n/a
@binwiederhier commented on GitHub (Feb 19, 2026):
Hi @caronc , thank you for Apprise!
What env are you testing this against? I would be highly surprised if this didn't work.
I ma on my phone tested it and it seems to work just fine:
@caronc commented on GitHub (Feb 19, 2026):
Issue originated from https://github.com/caronc/apprise/issues/1520. Adding tags into the payload fixed it (i left
X-Tagsuntouched).I'm not sure... perhaps the @kimimaru4000 can shed some light? In screenshots he/she provided, the
warningtag was what he used as an example was missing. Maybe i fixed a bug that wasn't a bug? 🙂@wunter8 commented on GitHub (Feb 19, 2026):
This just worked fine for me on ntfy.sh
@kimimaru4000 commented on GitHub (Feb 19, 2026):
From what I see in my notification Python script, the visual tags are used in the "Tags" header, as opposed to "X-Tags". Perhaps this is where the confusion lies?
@wunter8 commented on GitHub (Feb 19, 2026):
The visual "warning" tag was recognized just fine
@caronc commented on GitHub (Feb 19, 2026):
I will roll back my change if not needed (or if it doesn't hurt to double down on the entry in the payload as well i can leave it; it may be sloppy the way it is now. Perhaps issue is with @kimimaru4000's specific environment/configuration?
@caronc commented on GitHub (Feb 19, 2026):
Going to close this thread everyone. I'm very sorry for wasting your time. I really appreciate the fast responses!🙏🚀
@binwiederhier commented on GitHub (Feb 19, 2026):
You can ask 1000 questions, @caronc ❤️ -- People that make awesome things have infinite "dumb question quota" :-D