You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Paul Stanton <pa...@mapshed.com.au> on 2012/03/11 05:30:23 UTC
Re: Customising T5 URL Encoding
+1
possibly with 3 options? :
a) tomcat compatible default encoding
b) jetty compatible default encoding
c) tapestry encoding
On 21/06/2010 6:34 AM, Joel Halbert wrote:
> Agreed, it would be good to have this as a configuration option.
>
> On 20/06/10 19:20, Kai Weber wrote:
>> * Nicolas Bouillon<ni...@bouil.org>:
>>
>>> The Tapestry URL encoding is not a problem for me in general, just
>>> for one
>>> use case when i wanted to migrate a site to tapestry and keeping the
>>> same
>>> URL (with accents, spaces, dashes, underscores and so on).
>> It is a problem if you get called by other webapps. If they call your
>> page with the standard URL encoding scheme you have a problem. Say you
>> have
>>
>> onActivate(String emailadress)
>>
>> no one can call your page because the expected encoding for @ in T5 is
>> $0040 where the rest of the world would send you an @.
>>
>> We use only query strings or numerical IDs as parameters for pages which
>> can get called from external sites.
>>
>> I would like to see configuration option to switch or disable the
>> URLEncoder completly.
>>
>> Kai
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Customising T5 URL Encoding
Posted by Jochen Frey <jo...@jochenfrey.com>.
+1
On Mar 12, 2012, at 8:57 AM, David Canteros wrote:
> +1
> I have several problems with the integration of my Tapestry tools and other
> non-tapestry tools, all of this caused by tapestry URLEncoder. I solved
> this by overriding URLEncoder, but your proposal would be a more elegant
> solution
>
>
> ------------------------------------------------------------------
> David Germán Canteros
>
>
> 2012/3/11 Paul Stanton <pa...@mapshed.com.au>
>
>> +1
>>
>> possibly with 3 options? :
>>
>> a) tomcat compatible default encoding
>> b) jetty compatible default encoding
>> c) tapestry encoding
>>
>> On 21/06/2010 6:34 AM, Joel Halbert wrote:
>>
>>> Agreed, it would be good to have this as a configuration option.
>>>
>>> On 20/06/10 19:20, Kai Weber wrote:
>>>
>>>> * Nicolas Bouillon<ni...@bouil.org>:
>>>>
>>>> The Tapestry URL encoding is not a problem for me in general, just for
>>>>> one
>>>>> use case when i wanted to migrate a site to tapestry and keeping the
>>>>> same
>>>>> URL (with accents, spaces, dashes, underscores and so on).
>>>>>
>>>> It is a problem if you get called by other webapps. If they call your
>>>> page with the standard URL encoding scheme you have a problem. Say you
>>>> have
>>>>
>>>> onActivate(String emailadress)
>>>>
>>>> no one can call your page because the expected encoding for @ in T5 is
>>>> $0040 where the rest of the world would send you an @.
>>>>
>>>> We use only query strings or numerical IDs as parameters for pages which
>>>> can get called from external sites.
>>>>
>>>> I would like to see configuration option to switch or disable the
>>>> URLEncoder completly.
>>>>
>>>> Kai
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
---
jochen@jochenfrey.com
+1.415.366.0450
@jochen_frey
Re: Customising T5 URL Encoding
Posted by David Canteros <da...@gmail.com>.
+1
I have several problems with the integration of my Tapestry tools and other
non-tapestry tools, all of this caused by tapestry URLEncoder. I solved
this by overriding URLEncoder, but your proposal would be a more elegant
solution
------------------------------------------------------------------
David Germán Canteros
2012/3/11 Paul Stanton <pa...@mapshed.com.au>
> +1
>
> possibly with 3 options? :
>
> a) tomcat compatible default encoding
> b) jetty compatible default encoding
> c) tapestry encoding
>
> On 21/06/2010 6:34 AM, Joel Halbert wrote:
>
>> Agreed, it would be good to have this as a configuration option.
>>
>> On 20/06/10 19:20, Kai Weber wrote:
>>
>>> * Nicolas Bouillon<ni...@bouil.org>:
>>>
>>> The Tapestry URL encoding is not a problem for me in general, just for
>>>> one
>>>> use case when i wanted to migrate a site to tapestry and keeping the
>>>> same
>>>> URL (with accents, spaces, dashes, underscores and so on).
>>>>
>>> It is a problem if you get called by other webapps. If they call your
>>> page with the standard URL encoding scheme you have a problem. Say you
>>> have
>>>
>>> onActivate(String emailadress)
>>>
>>> no one can call your page because the expected encoding for @ in T5 is
>>> $0040 where the rest of the world would send you an @.
>>>
>>> We use only query strings or numerical IDs as parameters for pages which
>>> can get called from external sites.
>>>
>>> I would like to see configuration option to switch or disable the
>>> URLEncoder completly.
>>>
>>> Kai
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>