wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grigorov <mgrigo...@apache.org>
Subject Re: Redirects to external URLs do not work as expected when cookies are forbidden
Date Thu, 04 Apr 2013 13:24:08 GMT

I'm not familiar with http code 303 (see other) but if there is a problem
then you should ask in the forums of the used web container or web browser.
Wicket just sets response headers via Servlet APIs but the actual work is
done by the container - to set the header, and by the browser - to read the
value and interpret it.

On Thu, Apr 4, 2013 at 10:04 AM, Oliver Zemann <oliver.zemann@gmail.com>wrote:

> Hi
> I created a wicket quickstart:
> https://github.com/olze/WicketRedirect.git
> The SC_SEE_OTHER which is defined in the RFC for HTTP 1.1 (iirc Jan. 1997)
> was explaining that this should work (sending a post to the application
> which uses GET to get the page from the redirected URL) is not working, it
> says only 301 and 302 are allowed.
> Why?
> When using 301 it works as expected when cookies are disabled. When cookies
> are disabled and 302 is used, it redirects to the local site and not to the
> external one because of the missing Location header. Is this a bug or did i
> understand something wrong? I thought 302 should be used when wicket should
> redirect to an external URL.
> Thanks
> Oliver

Martin Grigorov
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message