Would that be a problem to encode urls? What are the downsides?
Christian
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Gunter
Sent: Friday, May 16, 2008 11:40 AM
To: Stripes Users List
Subject: [Stripes-users] More feedback needed
We have an open issue requesting that clean URL parameters be URL-encoded.
http://stripesframework.org/jira/browse/STS-559
This sounds like a good idea at first, but when URLEncoder encodes a string, it
appears to encode *anything* that is not alphanumeric. So if, for example, you
want a param that looks like "a,b,c" you're going to end up with "a%2Cb%2Cc".
If you've ever looked at a Yahoo link you know they use all kinds of URLs with
commas, semicolons and such in them. So we're not sure which way to go. What do
you all think?
-Ben
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
