Most UrlEncoding Strategies fail to encode "/" (and "\") in a practical way
---------------------------------------------------------------------------
Key: WICKET-1983
URL: https://issues.apache.org/jira/browse/WICKET-1983
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.4-RC1
Reporter: Andreas Sahlbach
Most UrlEncodingStrategies encode PageParameters simply by escaping the using
octed codes. For example a page parameter "a/b" will be encoded into "a%2Fb".
BookmarkablePageRequestTargetUrlCodingStrategy for example would generate an
URL that looks like this: http://localhost/mypage/bez/a%2Fb/ for a parameter
called "bez" and the value "a/b".
This is correct according to RFC 2396, but most http servers don't accept
encoded path separators for security reasons. (See e.g. apache option
AllowEncodedSlashes). My version of tomcat also does not accept these kind of
urls and delivers "Bad request" for such urls.
I would like to suggest to do some special double ecoding for these problematic
cases ("/" and "\" are affected I guess), so that no special options are needed
to be tweaked. Not sure if it's even possible to let tomcat server such an url.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
