Request.QueryString and Server.URLDecode()

[John Grandy]

Does Server.URLDecode() need to be applied to Request.QueryString(<key
name>) ?

 

[Lucas Tam]

Does Server.URLDecode() need to be applied to Request.QueryString(<key
name>) ?

Yes - if the string is encoded. Request.Querystring returns the raw
(undecoded) text.

 

[Sean M]

Yes, as I discovered this is also important when using Base64-encoded
strings in the QueryString. Here's what I use to combat frustration:

string sOKForBase64Decrypt =
Server.UrlDecode(Request.QueryString["argument"].ToString()).Replace("
","+")

-- Sean M

 

[John Grandy]

Hmmm ...

My tests don't show any need to apply Server.URLDecode() to
Request.QueryString()

I tested a return URL of

http://localhost/Results.aspx?search=here+are+some+spaces

Debug-mode stepping through the server-side code ,
Request.QueryString("search") contains the value "here are some spaces" (no
plus signs are included)

Yes, as I discovered this is also important when using Base64-encoded
strings in the QueryString. Here's what I use to combat frustration:

string sOKForBase64Decrypt =
Server.UrlDecode(Request.QueryString["argument"].ToString()).Replace("
","+")

-- Sean M

Does Server.URLDecode() need to be applied to Request.QueryString(<key
name>) ?

 

[Joerg Jooss]

Yes - if the string is encoded. Request.Querystring returns the raw
(undecoded) text.

Um... no. Items retrieved from the QueryString collection have already
been decoded (anything else would be disastrous).

Cheers,

 

[Lucas Tam]

Um... no. Items retrieved from the QueryString collection have already
been decoded (anything else would be disastrous).

Oops you're right : )

Always thought you needed to run it through Server.URLDecode.

 

[Lucas Tam]

Hmmm ...

My tests don't show any need to apply Server.URLDecode() to
Request.QueryString()

I think it may of been out of habit from ASP days???