[WICKET-4260] UrlRenderer renders invalid relative URLs if first segment contains colon

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.3
• Fix Version/s: 1.5.6, 6.0.0-beta2
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Andreas Köhler
• Created: 25/Nov/11 12:07
• Updated: 07/Mar/16 15:44
• Resolved: 07/Apr/12 06:20

Description

Seen on Wicket 1.5.3.

If a relative url of a link starts with a path segment containing a colon then the whole uri will be regarded as absolute uri, so typically browsers will complain that there is no handle for the protocol foo in foo:bar/dee/per.

See also the attached quickstart. The start page contains three links, one relative with colon, one absolute and one to a mounted page without colon for comparison.
The application also has a static switch to add an extended urlrenderer, prepending "./" if needed. This fix is merely a quick shot and there might be better alternatives.

Issue Links

• breaks: WICKET-4920 Rendered Url on root context with cookies disabled might result in double slash //
• is duplicated by: WICKET-4442 UrlEncoder does not encode colons in path segments
• relates to: WICKET-6111 Empty redirect on redirect to home page if home page already shown