Request.QueryString and Server.URLDecode()

[John Grandy]

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

[Lucas Tam]

"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in news:OVxu7q5nFHA.4056
@TK2MSFTNGP10.phx.gbl:

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.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[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" <johnagrandy-at-yahoo-dot-com> wrote in message
news:OV**************@TK2MSFTNGP10.phx.gbl...

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

[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...re+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)



"Sean M" <ta******@hotmail.com> wrote in message
news:O4**************@TK2MSFTNGP09.phx.gbl...

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" <johnagrandy-at-yahoo-dot-com> wrote in message
news:OV**************@TK2MSFTNGP10.phx.gbl...

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

[Joerg Jooss]

Lucas Tam wrote:

"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in
news:OVxu7q5nFHA.4056 @TK2MSFTNGP10.phx.gbl:

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.

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

Cheers,
--
http://www.joergjooss.de
mailto:ne********@joergjooss.de

[Lucas Tam]

"Joerg Jooss" <ne********@joergjooss.de> wrote in news:xn0e643z6a3rc8n004
@msnews.microsoft.com:

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).

Oops you're right : )

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

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Lucas Tam]

"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in news:ueSagefoFHA.3256
@tk2msftngp13.phx.gbl:

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???

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/