You can look at the response headers and see where the redirect is coming from. You can also view source on the response (all from tamper data) and see what it is exactly.
For instance, I have a server that requires HTTPS. So, I use Apache to redirect all port 80 requests to the port 443 equivalent. Then, if it was "/" that was requested, Wicket takes over and does a redirect to the homepage. The first redirect shows "Apache (CentOS)" as the server header response. The second (Wicket) shows "Apache-Coyote" - my servlet container. Hope this helps.... -- Jeremy Thomerson http://www.wickettraining.com On Wed, Sep 10, 2008 at 11:14 AM, 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] > >
