this post was submitted on 09 Jul 2024
22 points (100.0% liked)
Programming
16769 readers
95 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Can you elaborate on that? The X- prefix is supposedly only a recommendation, and intended to be used in non-standard, custom, ah-hoc request headers to avoid naming conflicts.
Taken from https://datatracker.ietf.org/doc/html/rfc6648
I still work on software that extendively uses X- headers.
The RFC you linked recommends that no new
X-
prefixed headers should be used.The paragraph you quoted does not say you should use the
X-
prefix, only comments on how it was used.See section 3 for the creation of new parameters: https://datatracker.ietf.org/doc/html/rfc6648#section-3
I wouldn't worry too much about it. The reason they give is mostly that it is annoying if a
X-
header suddenly becomes standardized and you end up having to supportX-Something
andSomething
. Most likely a non-issue with real custom headers.