https://issues.apache.org/bugzilla/show_bug.cgi?id=53469
--- Comment #9 from Mark Thomas <ma...@apache.org> --- (In reply to comment #8) > The problem lies in the fact that encodeURL rewrites the url to absolute. I > think this should only be done in encodeRedirectURL. That is a fair point. We'll get that addressed for the next release. However... > Wicket also calls > encodeURL to encode urls that are rendered in hrefs on the response page. > Tomcat rewriting them to absolute breaks this badly. That suggests something else is going on that I'd like to get to the bottom of. > Suppose you are at /a/b and you click a link to /a/b/c/d. This page contains > a link to /1/2. Wicket renders all urls relative, so the link to /1/2 will > be ../../../1/2 (it is relative to /a/b/c/d). This link will be passed to > Response.encodeURL, which rewrites it to /a/../../../1/2, which obviously is > wrong and fails. Huh? If you click a link to /a/b/c/d and the response contains a relative link ../../../1/2 then the result should be /a/b/c/../../../1/2 == /1/2 (i.e. relative to the current request). Why does Tomcat/Wicket think it should be relative to the previous request for /a/b ? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
