Thanks for Jon's informative inputs.
Hi Alex,
Since your concern here is to avoid those URL sensitive chars in your
querystring value(encrypted through 3DES CSP), I think you can also
consider performing UrlEncoding on the encrypted querystring value(even if
you're using BASE64 convertion). And the HttpUtility.UrlEncode method just
help perform url encoding on a give string(which will replace any chars
which are not allowed in url with escaped values)
#HttpUtility.UrlEncode Method (String)
http://msdn2.microsoft.com/en-us/library/4fkewx0t.aspx
Hope this also helps some.
Regards,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)