I always fixed it by a filter until now. What about adding a filter in tomcat and if users complain move to another solution? Can even be marked @Alpha for a few I guess.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le jeu. 4 févr. 2021 à 17:55, Mark Thomas <ma...@apache.org> a écrit : > On 04/02/2021 16:37, Romain Manni-Bucau wrote: > > (if it helps) From what I saw which was close to that it was due to the > > current microservice erea where it is very common to have poor man > proxies > > coded in java/tomcat and forwarding all headers of a HTTP request, this > is > > not uncommon and will even work on some containers (and always in bad > tests > > ;)) but nothing a filter can't fix trivially. > > That is the scenario I am looking at. If your experience is that a > filter is (nearly) always safe in those scenarios then that is the way > to go. > > Thanks, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
