http://blogs.msdn.com/b/spatdsg/archive/2010/10/29/love-the-tubes-thank-you-kiran-patil-base64-won-t-trick-me-again.aspxThank God for the tubes!! I was banging my head against some errors today in some code which seemed pretty straightforward. Take some data - encrypt it via 3DES - encode it in base64 Toss it over to some other system - decode - decrypt. en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/spatdsg/archive/2010/10/29/love-the-tubes-thank-you-kiran-patil-base64-won-t-trick-me-again.aspx#10109918Wed, 29 Dec 2010 17:04:42 GMT91d46819-8472-40ad-a661-2c78acb4018c:10109918SpatDSG<p>The client really wasnt a browser for testing - in this case I could not use HttpServerUtility</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10109918" width="1" height="1">http://blogs.msdn.com/b/spatdsg/archive/2010/10/29/love-the-tubes-thank-you-kiran-patil-base64-won-t-trick-me-again.aspx#10086256Thu, 04 Nov 2010 18:28:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:10086256Nick<p>What sounds to me like a better solution would be to UrlEncode the value placed in the query string, rather than replace char which where UrlDecoded when reading from the query string.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10086256" width="1" height="1">