Thanks to everyone who has suggested solutions. It turns out that the issue is stranger than I thought, and it's not Wicket-specific. I'll share what we've got, in case it helps anyone else (not that we have a solution yet.)
We have a load balancer, Apache, and Tomcat handling requests. When any servlet application is called, for example, https://jprod01.chemeketa.edu/docs/ (which is one of the sample apps that installs with Tomcat), it display perfectly fine if it has the "/" after docs. But if the URL is https://jprod01.chemeketa.edu/docs (without the "/") then browser automatically gets redirected to http://jprod01.chemeketa.edu/docs/ (with the "/" but without the "s" in "https"). Why? Who knows. Rikard Lindström wrote: > > I have the same problem as above, and by using the Tamper Data plugin I > get similar results. > A request to https flips to http. Everything works ofc if both protocols > are opened, but in production mode we only use https :( > Do you have any ideas how to solve this issue? > -- View this message in context: http://www.nabble.com/https-flips-to-http-tp19403303p19435935.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
