Setting the following security-constraint in your web.xml should fix that:
<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
It basically enforces ALL requests to SSL connections.
Jörn
On Wed, Sep 10, 2008 at 6:14 PM, insom <[EMAIL PROTECTED]> wrote:
>
> Here's what I see from using Tamper Data. It appears that there's a 302
> redirect causing the switch. Is that something Wicket does?
>
> http://www.nabble.com/file/p19414977/tamperData.gif
>
>
>
> Jeremy Thomerson-5 wrote:
>>
>> Wicket uses relative URLs, so at first guess, I'd think it was something
>> else. Start with something like
>
> --
> View this message in context:
> http://www.nabble.com/https-flips-to-http-tp19403303p19414977.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]
>
>
