[GH-ISSUE #1617] Header X-Tags is not honored #1134

Closed
opened 2026-05-07 00:30:29 +02:00 by BreizhHardware · 8 comments

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-Tags which does not appear to work. However setting tags in the JSON payload does work.

Would advise to either support X-Tags as documented or just drop it from documentation since the payload method works fine too. All other X-Header-Options appear to be correctly honored.

note: I did not test Tags on 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

Originally created by @caronc on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1617 :lady_beetle: **Describe the bug** Ntfy documentation identifies the use of setting `X-Tags` which does not appear to work. However setting `tags` in the JSON payload does work. Would advise to either support `X-Tags` as documented or just drop it from documentation since the payload method works fine too. All other `X-Header-Options` appear to be correctly honored. **note:** I did not test `Tags` on it's own. [Apprise workaround in place works fine using tags in payload](https://github.com/caronc/apprise/pull/1524) :computer: **Components impacted** all :bulb: **Screenshots and/or logs** n/a :crystal_ball: **Additional context** n/a
BreizhHardware 2026-05-07 00:30:29 +02:00
  • closed this issue
  • added the
    🪲 bug
    label
Author
Owner

@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:

Image

Image

<!-- gh-comment-id:3927356281 --> @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: ![Image](https://github.com/user-attachments/assets/dae77e9c-4121-48c8-96ea-ba96d7e28c8d) ![Image](https://github.com/user-attachments/assets/12edef0c-655d-4c1e-b30f-fc171e8ffe05)
Author
Owner

@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-Tags untouched).

Image

I'm not sure... perhaps the @kimimaru4000 can shed some light? In screenshots he/she provided, the warning tag was what he used as an example was missing. Maybe i fixed a bug that wasn't a bug? 🙂

<!-- gh-comment-id:3927427329 --> @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-Tags` untouched). <img width="987" height="232" alt="Image" src="https://github.com/user-attachments/assets/0c4874a1-5245-4cce-a883-62db5f6abb17" /> I'm not sure... perhaps the @kimimaru4000 can shed some light? In screenshots he/she provided, the `warning` tag was what he used as an example was missing. Maybe i fixed a bug that _wasn't a bug_? 🙂
Author
Owner

@wunter8 commented on GitHub (Feb 19, 2026):

This just worked fine for me on ntfy.sh

$ curl -H "X-Tags: warning,tag2" -d "test message" https://ntfy.sh/tag-test
{"id":"oVJhD2W3nLRO","time":1771509429,"expires":1771552629,"event":"message","topic":"tag-test","message":"test message","tags":["warning","tag2"]}
<!-- gh-comment-id:3927480827 --> @wunter8 commented on GitHub (Feb 19, 2026): This just worked fine for me on ntfy.sh ``` $ curl -H "X-Tags: warning,tag2" -d "test message" https://ntfy.sh/tag-test {"id":"oVJhD2W3nLRO","time":1771509429,"expires":1771552629,"event":"message","topic":"tag-test","message":"test message","tags":["warning","tag2"]} ```
Author
Owner

@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?

<!-- gh-comment-id:3927499953 --> @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?
Author
Owner

@wunter8 commented on GitHub (Feb 19, 2026):

The visual "warning" tag was recognized just fine

Image
<!-- gh-comment-id:3927524925 --> @wunter8 commented on GitHub (Feb 19, 2026): The visual "warning" tag was recognized just fine <img width="1280" height="500" alt="Image" src="https://github.com/user-attachments/assets/5962dd95-d1b6-444a-8ff4-e584b693492b" />
Author
Owner

@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?

<!-- gh-comment-id:3927617837 --> @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?
Author
Owner

@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!🙏🚀

<!-- gh-comment-id:3929453108 --> @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!🙏🚀
Author
Owner

@binwiederhier commented on GitHub (Feb 19, 2026):

You can ask 1000 questions, @caronc ❤️ -- People that make awesome things have infinite "dumb question quota" :-D

<!-- gh-comment-id:3929460630 --> @binwiederhier commented on GitHub (Feb 19, 2026): You can ask 1000 questions, @caronc ❤️ -- People that make awesome things have infinite "dumb question quota" :-D
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#1134
No description provided.