I need to redirect to a url passing a parameter as a query string.
This can include an Ampersand in the value. such as
string value = "This & That";
Response.Redirect("http://www.example.com/?Value=" + Server.UrlEncode(value));
This however returns http://www.example.com/?Value=This+&+That
What should I be using to encode this string?
EDIT: Thanks Luke for pointing out the obvious, the code does indeed work correctly. I Apologise, my question was not a valid question after all!
The page I was going to had a lot of old legacy code which is apparently doing some kinda of encoding and decoding itself making it appear as if my urlencode was not working.
My solution unfortunately is to completely drop use of an & until the code in question can be re-written. Don't you just hate old code!
Another character that needs escaping is the apostrophe. Replace it with %27.
string url = Server.UrlEncode(value).Replace("'", "%27);
HttpUtility.UrlEncode() And Server.UrlEncode() do not replace this character along with a few others for backwards compatibility with other .Net Frameworks. See this microsoft article for details: http://connect.microsoft.com/VisualStudio/feedback/details/214349/httputility-urlencode-does-not-encode-apostrophe
this is correct however if you have several parameters in the query string.
for example : &firstname=bob&secondName="Tracy and John"
And if you are getting a value from a
GridView
the& ampersand
may very well be showing up as"&"
:So in this case you will want to use:
The documentation suggests that
Server.UrlEncode
should handle ampersands correctly.I've just tested your exact code and the returned string was correctly encoded:
Technically doing:
will do the trick.
EDIT: There seem to be some tricky issues with the whole UrlEncode/HttpEncode methods that don't quite do the trick. I wrote up a simple method a while back that may come in handy. This should cover all the major encoding issues, and its easy to write a "desanitizer" as well.
You must use
Server.UrlEncode(string containing the ampersand)
.I've just tested it and the returned query string was correctly encoded and then decoded.
HttpUtility
didn't work for this operation.