This content has been marked as final. Show 6 replies
Did you try the URLEncodedFormat()/URLDecode() functions that escapes
URL special characters so that the can be passed through a request?
Thanks it works......
i completely forgot of these func.
If you do decide to use the "DES" or "AES" libraries for your encryption (not a bad idea since they are stronger than CFMX_Compat), you may want to consider compartmentalizing your encryption / decryption functions into a component. Once you generate a key using generatesecretkey, you can store it in your code as a private variable in your component. That way any page would be able to encrypt / decrypt in your application without exposing your key.
but if I store in a component and I have to restart the server I loose the key.
Maybe I can generate once and store in the settings xml file and periodically change that.
Sounds ok to me
What you think about that??
I was actually suggesting that you hard code the text of the key in the CF code in your component. I suppose you could store the data in a settings file and then parse it out if you wanted to, but it seems like adding an extra step into the equation.
I solved it.
I created a des secret key and stored that in my application xml settings file and using that in my code.
I prefer this encoding than the cf default that works with too much "strange" caracter that can create confusion in coding .