See http://www.petrikainulainen.net/programming/tips-and-tricks/wicket-https-tutorial-part-three-creating-a-secure-form-submit-from-a-non-secure-page/
On Sun, Jan 15, 2012 at 10:51 AM, Per Newgro <[email protected]> wrote: > Thanks for testing this out. I wasn't aware of that. > > I didn't understand the usecase exactly. You want to set the page / request > secure > if you've added the login form? Or do you want to secure the form only. > For the later a possible answer is this > http://stackoverflow.com/questions/96164/partial-site-ssl-using-asp-net-login-control > It's a .net answer but the issue seems to be the same. > > Per > > Am 15.01.2012 01:41, schrieb armhold: > >> Hi Per, >> >> The documentation for @RequireHttps implies that it only works for pages, >> not components, and my (limited) testing shows that to be the case. Is >> there >> a way to use it with components on otherwise insecure pages? >> >> My use case is to secure a form on non-https pages, specifically to secure >> that very nice username/password field at the top of Twitter Bootstrap >> pages. >> >> Thanks >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/how-to-get-https-port-number-in-Wicket-1-5-tp4295139p4296003.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
