C
Chris
Just a curiosity:
Is it standard practice to UrlEncode and UrlDecode cookie values? I
wouldn't have even stumbled across this except I noticed that when I
retrieve a cookie that was set with ASP and had an asterisk in it, ASP
UrlEncoded it ("%2A"). I was forced to UrlDecode the cookie in my
ASPX page. As the Values collection is a NameValueCollection (not
directly related to the HttpCookie class), I can understand that
adding a value in .NET would do it verbatim ("*").
Not a big deal, but is it "standard" to UrlEncode strings before
adding them to the .Values NameValueColection of a HttpCookie?
Is it standard practice to UrlEncode and UrlDecode cookie values? I
wouldn't have even stumbled across this except I noticed that when I
retrieve a cookie that was set with ASP and had an asterisk in it, ASP
UrlEncoded it ("%2A"). I was forced to UrlDecode the cookie in my
ASPX page. As the Values collection is a NameValueCollection (not
directly related to the HttpCookie class), I can understand that
adding a value in .NET would do it verbatim ("*").
Not a big deal, but is it "standard" to UrlEncode strings before
adding them to the .Values NameValueColection of a HttpCookie?