utf-8 content in urls
---------------------
Key: TAP5-539
URL: https://issues.apache.org/jira/browse/TAP5-539
Project: Tapestry 5
Issue Type: Improvement
Affects Versions: 5.0.18, 5.0.17, 5.1
Reporter: Grigoris Ioannou
Priority: Minor
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
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
