As long as your custom scheme can also handle UTF-8 standard scheme so that
libraries that we integrated with (JS libraries and others) that produce
encoded URLs don't break.
----- Original Message -----
From: "Massimo Lusetti" <[EMAIL PROTECTED]>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Saturday, October 25, 2008 6:22 PM
Subject: Re: The URL encoding issue
On Fri, Oct 24, 2008 at 7:01 PM, Howard Lewis Ship <[EMAIL PROTECTED]>
wrote:
BTW,
I'm actively working on the issue with URL encoding/decoding. Because
of the differences between Jetty and Tomcat, I'm abandoning standard
URL encoding (i.e., %2f and all that) and using my own scheme.
As a side effect, we can now properly support null and blank string
values in page activation and event contexts (they will appear in URLs
as $N and $B, respectively).
It's somehow between strange and sad to have this issues again and
again but that seems to have come out nice, as usual.
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
