[TAP5-539] utf-8 content in urls

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 5.1, 5.0.17, 5.0.18
• Labels: bulk-close-candidate
• Assignee: Unassigned
• Reporter: Grigoris Ioannou
• Created: 26/Feb/09 14:44
• Updated: 09/Mar/16 11:55
• Resolved: 16/Jul/15 07:51

Description

When utf-8 encoded content is passed in a url, the url gets ugly.

For instance, urls similar to

http://localhost:8080/app/viewcity/Krak$00f3w-Poland-Europe/9584
and
http://localhost:8080/app/viewcity/N$00eemes-France-Europe/7196

are ugly and should appear as such:

http://localhost:8080/app/viewcity/Kraków-Poland-Europe/9584
and
http://localhost:8080/app/viewcity/Nîmes-France-Europe/7196

(If the urls are still ugly in the browser, the utf-8 content is still not displayed correctly. Hover the mouse over them, or click 'Edit this issue' and look at the description, you will see how it should be)

This behaviour was changed in some version I can't recall to provide better support for null and empty activation context parameters.

There is a Tapestry service, org.apache.tapestry5.services.URLEncoder, that does the activation context -> string and string -> activation context encoding. You can write your own and override the one used by Tapestry through the alias overriding feature described here: http://tapestry.apache.org/tapestry5/guide/alias.html.

I guess Tapestry could provide an easy way to switch between the old and the new activation context encoding.

Issue Links

• is related to: TAP5-2225 Create client-side API to call a component's event handler methods
• relates to: TAP5-1803 URL encoding in ActivationRequestParameter is very strict