https://bz.apache.org/bugzilla/show_bug.cgi?id=59779
--- Comment #4 from NateC <apa...@neworld.us> --- (In reply to Mark Thomas from comment #3) > (In reply to NateC from comment #2) > > (In reply to Mark Thomas from comment #1) > > > > > I don't understand the problem. I think a concrete example is required. > > > > An example Connector configuration which would have this issue: > > <Connector > > protocol="org.apache.coyote.http11.Http11AprProtocol" > > port="80" > > secure="true" > > scheme="https" > > proxyPort="443" > > URIEncoding="UTF-8" > > /> > > > > When a client makes a request to http://example.com/servlet/index.html and > > the servlet performs a redirect to "landingPage.html" when constructing an > > absolute URL the redirect is to > > "https://example.com:443/servlet/landingPage.html"; but when it is relative > > the url is just "landingPage.html", which the client will interpret as > > "http://example.com/servlet/landingPage.html"; > > Either there is a reverse proxy missing from the above description or scheme > and proxyPort are being mis-used to generate redirects to https when a > transport guarantee should be used. This configuration is being used behind a load balancer performing SSL offloading. Looking at the connector doc, https://tomcat.apache.org/tomcat-7.0-doc/config/http.html it looks like this should work based on this description. The proxyName and proxyPort attributes can be used when Tomcat is run behind a proxy server. These attributes modify the values returned to web applications that call the request.getServerName() and request.getServerPort() methods, which are often used to construct absolute URLs for redirects. -- 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
