https://issues.apache.org/bugzilla/show_bug.cgi?id=55734
--- Comment #3 from Mark Thomas <ma...@apache.org> --- The developer is doing exactly what they should do - using request.getContextPath() to correctly construct the URL. The breakage occurs in the proxy because the proxy is changing the path and the application has no way of knowing the path has been changed. Changing the context path in the proxy is something pretty much guaranteed to break all but the most trivial of web applications. If an sys admin decides to change the path in the proxy then they need to change it for both inbound and outbound traffic. The simplest solution is to change the context path in the back-end server to match the context path used by the proxy. In your example renaming $CATALINA_BASE/webapps/manager to $CATALINA_BASE/webapps/some#other#path is the change required. The complex solution is to use mod_proxy, mod_headers and mod_substitute (or equivalent) to fix the headers and the content. If the manager app generates URLs that start with "/manager" when deployed under a different path that would be a valid bug. -- 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