3 ms·
What a wonderful idea. I have just updated out frontend server config to include the header. On thing though: According to RFC6648, we should not be using the
by pilif 10y ago
What a wonderful idea. I have just updated out frontend server config to include the header.
On thing though: According to RFC6648, we should not be using the X- prefix any more for custom headers (https://tools.ietf.org/html/rfc6648 https://tools.ietf.org/html/rfc6648), but I guess it's too late to change this now.
- poizan42 10y agoIt says: > 1. Deprecates the "X-" convention for newly defined parameters in application protocols, including new parameters for established protocols. This change applies even where the "X-" convention was only implicit, and not explicitly provided, such as was done for email in [RFC822]. It says for application protocols. I would argue in this case that it's not any part of an application protocol as the header is never used for anything.
- qwertyuiop924 10y ago>1. Deprecates the "X-" convention for newly defined parameters in application protocols, including new parameters for established protocols. This has already been defined, so we're in the clear, I think.
- pilif 10y agoRFC6648 is from 2012 though, but Sir Terry Pratchett died in 2015, which is when this initiative started. As such it's violating RFC6648 because it continues to use the X- prefix.
- qwertyuiop924 10y agoCrap. Oh well. We're violating an RFC. What's the IETF going to do about it? Nothing.