Then maybe you'll need to modify org.apache.wicket.protocol.https.HttpsRequestCycleProcessor.checkSecureIncoming(IRequestTarget) to your needs.
On Thu, Oct 21, 2010 at 9:56 AM, sonxurxo <sonxu...@gmail.com> wrote: > > I use some secure pages annotated with @RequireHttps, but not all the pages > where the login panel will be. For example, the main page or the "general > info page" will be no secured, but the login panel will be there in both > pages. There are also other "profile-dependent" pages that are of course > full secured, and others -as I mentioned in an older post, the registration > page is an example-. > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/SSL-Links-and-buttons-tp3001634p3005153.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
