The solution seems to be an extra header with the mod_header module and an extra filter before the wicket filter. With the later we can check the extra header, and overwrite the scheme to "https" if the header is present. Seems to be working for now...
Regards, Istvan On Thu, Mar 4, 2010 at 6:04 PM, Istvan Soos <istvan.s...@gmail.com> wrote: > Hi, > > We are using HttpsRequestCycleProcessor + @RequireHttps annotation in > our local dev environment (the server is a jetty executed directly > from Eclipse). In the production environment, we have Apache + > mod_proxy, and I'd prefer if Apache could handle the SSL part (in that > case we are not required to configure SSL on the application server - > glassfish v3). Is there any best practice how to achieve this? > > Thanks and regards, > Istvan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
