You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Grigoris Ioannou (JIRA)" <ji...@apache.org> on 2009/02/26 15:45:01 UTC
[jira] Created: (TAP5-539) utf-8 content in urls
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.
[jira] Commented: (TAP5-539) utf-8 content in urls
Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770776#action_12770776 ]
Kalle Korhonen commented on TAP5-539:
-------------------------------------
Allowing contributions to the safe characters or at least implementing protected getSafe() so you wouldn't need to duplicate the whole URLEncoder would go a long way
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-539) utf-8 content in urls
Posted by "Grigoris Ioannou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grigoris Ioannou updated TAP5-539:
----------------------------------
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. 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.
was:
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.
> 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
>
> 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. 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-539) utf-8 content in urls
Posted by "Grigoris Ioannou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grigoris Ioannou updated TAP5-539:
----------------------------------
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.
was:
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. 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.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-539) utf-8 content in urls
Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770776#action_12770776 ]
Kalle Korhonen commented on TAP5-539:
-------------------------------------
Allowing contributions to the safe characters or at least implementing protected getSafe() so you wouldn't need to duplicate the whole URLEncoder would go a long way
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-539) utf-8 content in urls
Posted by "Grigoris Ioannou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grigoris Ioannou updated TAP5-539:
----------------------------------
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.
was:
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. 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.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-539) utf-8 content in urls
Posted by "Grigoris Ioannou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grigoris Ioannou updated TAP5-539:
----------------------------------
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. 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.
was:
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.
> 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
>
> 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. 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.