https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
--- Comment #7 from Christopher Schultz <ch...@christopherschultz.net> --- I'm curious why this enhancement has even been requested. My understanding of the HTTP spec is that the "Host" header should not be modified by an intervening reverse-proxy. https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23 If you request http://example.com/application/path, then the client RFC-MUST supply "Host: example.com" in the headers and any reverse-proxy RFC-MUST forward that "Host: example.com" header on to the origin server. What reverse-proxy are you using which changes the "Host" header? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
