On Mon, 07 Nov 2011 14:10:28 -0200, Martin Strand <do.not.eat.yellow.s...@gmail.com> wrote:

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.

I guess you won't have any problems. As far as I can remember, the URLEncoder old implementation didn't have any character encoding besides URL encoding. It was changed to deal with slashes and null and blank page activation context values better than before. I don't know why any non US-ASCII character is encoded, though.

--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to