I would try to avoid the whole double encoding business altogether. I imagine that whatever view technology you're using has a way to build URLs, much in the same way that you can build SQL query's using prepared statements. Prepared URLs, if you will.
throws errors about the parameter bleugh and formatting or some such thing, we implemented this solution a couple of years ago so can't remember the exact error.
Stephan van Hulst
posted 4 years ago
You could write a function that takes an URI without query string, and an associative array mapping query parameter names to values.
Use encodeURI() on the URI, and use Ext.urlEncode() on the associative array. You can then just paste the two results together with a "?" and you're done.
I have been playing with this this morning, and your right it isn't overly complicated.
I was hoping somebody was going to say don't bother IIS is being silly, but actually the code impact isn't too big yet
this is supposed to be a surprise, but it smells like a tiny ad: