By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,558 Members | 1,673 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,558 IT Pros & Developers. It's quick & easy.

Querystring Encryption

P: n/a
Hi.

I am trying to encrypt some data being passed between two
aspx pages using querystring. I have tried bith DES and
Rijndael and have run across the following problem.
After either provider encrypts the data I URL encode the
data. Once the data makes it to the next page I URL
decode the data prior to decrypting it.

The problem occurs when the original encryption includes
the + sign. The URL decode assumes this was put there by
the URL encode and replaces it with a space which causes
the decryption to fail. I have worked around this by
replacing any spaces with + prior to decryption.
However, this doesn't seem like an ideal solution as
there might be other characters that might be decoded
improperly. Has anyone found a work around for this
other than using basic Base64 encryption?

Thanks in advance for any input.

Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
This useful?

http://www.dotnetjunkies.com/HowTo/9...75836DC72.dcik

Greg
"Ryan" <an*******@discussions.microsoft.com> wrote in message
news:22****************************@phx.gbl...
Hi.

I am trying to encrypt some data being passed between two
aspx pages using querystring. I have tried bith DES and
Rijndael and have run across the following problem.
After either provider encrypts the data I URL encode the
data. Once the data makes it to the next page I URL
decode the data prior to decrypting it.

The problem occurs when the original encryption includes
the + sign. The URL decode assumes this was put there by
the URL encode and replaces it with a space which causes
the decryption to fail. I have worked around this by
replacing any spaces with + prior to decryption.
However, this doesn't seem like an ideal solution as
there might be other characters that might be decoded
improperly. Has anyone found a work around for this
other than using basic Base64 encryption?

Thanks in advance for any input.

Nov 21 '05 #2

P: n/a
I saw this site during my research of this problem. I
took a look at it but I'm concerned that it is simply a
wrapper of existing crypto service providers that would
suffer from the same problem.

Thanks for the input

-----Original Message-----
This useful?

http://www.dotnetjunkies.com/HowTo/99201486-ACFD-4607- A0CC-99E75836DC72.dcik
Greg
"Ryan" <an*******@discussions.microsoft.com> wrote in messagenews:22****************************@phx.gbl...
Hi.

I am trying to encrypt some data being passed between two aspx pages using querystring. I have tried bith DES and Rijndael and have run across the following problem.
After either provider encrypts the data I URL encode the data. Once the data makes it to the next page I URL
decode the data prior to decrypting it.

The problem occurs when the original encryption includes the + sign. The URL decode assumes this was put there by the URL encode and replaces it with a space which causes the decryption to fail. I have worked around this by
replacing any spaces with + prior to decryption.
However, this doesn't seem like an ideal solution as
there might be other characters that might be decoded
improperly. Has anyone found a work around for this
other than using basic Base64 encryption?

Thanks in advance for any input.

.

Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.