We use dots in some of our custom HTTP headers, for instance X-NXenrichers.document, X-NXfetch.entity or X-NXtranslate.entity. These are legal according to the HTTP spec, but nginx by default doesn't allow them (or underscores for that matters). And this is a problem for customers using nginx.
A workaround is to configure nginx with ignore_invalid_headers and underscores_in_headers but this is still something easily forgotten.
So we should use something more mainstream as a separator, just a -. This requires changing all clients and server parsing, but keeping the . for a while for backward compatibility. (The server code is mostly in RenderingContextImpl.)
See https://trac.nginx.org/nginx/ticket/629#comment:2 for a discussion by nginx maintainers as why they won't change their behavior.
- depends on
-
ELEMENTS-9 Don't use dots in custom HTTP headers
-
- Resolved
-
- is related to
-
ELEMENTS-1133 Don't use dots in custom HTTP headers
-
- Resolved
-
-
-
- Resolved
-
- is required by
-
-
- Resolved
-
