[jira] [Updated] (TAP5-539) utf-8 content in urls

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-539:
--------------------------------
    Labels: bulk-close-candidate  (was: tapestry5-review-for-closing)

This issue has been last updated more than a year ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-26, available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> 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.1, 5.0.17, 5.0.18
>            Reporter: Grigoris Ioannou
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)