>On 05/02/2019 08:23, Johan Compagner wrote: >> problem is that our customers are doing this. >> also they can have 1 tomcat with a few webapps that they want to map under >> different domains >> >> so that would mean for them starting 3 different tomcats under 3 different >> ports and configure all that >> thats not always something they want to do. >> So i guess the only way for me is to have some kind of setting (per context) > >They would be better configuring Tomcat with virtual hosts and having >three ROOT webapps. > >Mark
Dear Johan, as Christopher and Mark wrote: If possible in any way, please avoid to handle it via rewriting on a reverse proxy and prefer to set up the Tomcat to serve the application on the same domain and context path as used "outside" in front of the proxy. If you real can't avoid, you have to do a forward rewriting of the used header (e.g. hostname) and/or URL pattern in the one hand, but also a complex backward rewriting of the answer! You have to back-rewrite parts of the answer header (Cookies, Locations, Links, ...) and the embedded URLs in the content of different MIME types (HTML, CSS, javascript, JSON, ...). As a consequence, you have either to forbid compression of the returned body or (even more complex) decompress/modify/recompress it on the fly. Sometimes, I simply can't avoid because we need to have an application available on two "addresses" while migration or something similar. And if the application itself can't be run in two instances I know no other way. But's it a real burden every time. with greetings Guido
