On Mon, 07 Nov 2011 07:46:47 +0100, Kalle Korhonen <kalle.o.korho...@gmail.com>
wrote:
There's not been a T5 project where I haven't needed to override
URLEncoder service. Take a look at T5's URLEncoderImpl, override it
with your version and mark whichever characters you prefer as safe
(i.e. not encoded).
Kalle
I changed the default URLEncoder to assume everything is "safe" except for a
few characters:
static final String ENCODED_NULL = "$N";
static final String ENCODED_BLANK = "$B";
private final BitSet unsafe = new BitSet(128);
{
markUnSafe("/+$");
}
Just wondering, can you see any potential problems with this? I'm guessing
there's a reason Tapestry doesn't do this by default.
We have a number of search result pages in a variety of languages, and we'd
like Googlebot to see the search query properly encoded in the URL.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
