Closed GlennRicaud closed 4 years ago
NB, so the expiration only applies to the Google load balanser. Thing is that headers are actually case insensitive
We can not and must not do any breaking changes
Request Headers used by Enonic XP:
From the HttpServletRequest: Headers like "Range" or "Referer" used by AttachmentHandler or IssueResource are camel cased by Jetty -> OK "X-Forwarded-*"" headers are not but the getHeader is case insensitive -> OK
WebRequest/PortalRequest: Only specific header usage found is for "Range" and it is camel cased as mentioned above -> OK
Only impact found would then be for the Applications for the headers that are note renamed by Jetty.
Starting from September 30th, header names will be lowercased by GCP Check impact and adapt if required Fix in master and 6.15 branch