[
https://issues.apache.org/jira/browse/WICKET-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg updated WICKET-2728:
----------------------------------
Fix Version/s: 1.5-M1
unfortunately in reality it is not so simple. many people run their webapps
behind proxies with url rewriting. this is the main reason why wicket tries to
use relative urls for everything. we cannot construct an absolute url manually
without the user's help because we do not know the proxy/url rewriting scheme
they use. that said, while the spec says that only absolute urls should be used
all browsers seem to understand relative urls, specs are written against the
perfect world, apps are built against the real one.
i suppose we can intoduce a method into request to allow users a chance to
rewrite a relative url into an absolute during a redirect. assigning this to 1.5
also note that wicket-2600 did not change wicket to use absolute to relative,
wicket never used absolute urls for redirects unless you consider the "./"
syntax as absolute....
> Location headers (redirects) should be absolute, not relative URLs
> ------------------------------------------------------------------
>
> Key: WICKET-2728
> URL: https://issues.apache.org/jira/browse/WICKET-2728
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Sebb
> Fix For: 1.5-M1
>
>
> See WICKET-2600. I think the fix is wrong.
> Location URLs are supposed to be absolute:
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.30
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
