+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<nico...@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-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
