[WICKET-1983] Improve encoding of forward and backward slashes

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.4-RC1
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Bla Bla
• Created: 16/Dec/08 20:44
• Updated: 01/Feb/09 19:15
• Resolved: 01/Feb/09 19:15

Description

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 serve such an url.

Issue Links

• duplicates: WICKET-1303 Slash separated URL's cannot have URL parameters with value containing forward slash '/'