[TAP5-302] URL encoded strings that contain symbols such as %2f (encoded "/") are decoded incorrectly in some environments

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.0.16
• Assignee: Howard Lewis Ship
• Reporter: Martijn Brinkers
• Created: 15/Oct/08 16:57
• Updated: 28/Oct/08 20:07
• Resolved: 25/Oct/08 18:35

Description

If an activation context variable contains %2f (URL encoded /) it is interpreted as / and therefore interpreted as a separation of context variables.

example:

http://www.example.com/test/one/t%2fwo

I expect the above URL to contain three context variables nl: test, one and t/wo but Tapestry thinks it contains four context variables nl: test, one, t and wo

This makes it impossible to use Base64 encoded context variables because they can contain the / symbol (which is gets URL encoded to %2f)

Issue Links

• incorporates: TAP5-32 It is not possible to include a null or blank field as part of an event or page activation context
• relates to: TAP5-312 Tapestry should allow null values and blank strings to be encoded as an event or page activation context; currently this causes runtime exceptions