URLEncodedFormat will only change specific characters. So, if you pass
it the string "my string", all you'll get out is "my%20string".  Also,
it doesn't take a seed parameter. The second [optional] parameter is
for the character set. (I believe that pre-MX, it didn't even take
that second parameter at all0.

http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/funca114.htm#wp1114140

The URLencrypt UDF would actually "encrypt" the characters that
URLEncodedFormat skips (such as letters and numbers).

Personally, I don't see a lot of need for the URLEncrypt().  If they
can break your security just by changing a URL parameter, you may have
bigger issues. (Unless there's ano issue I'm not thinking of)

Scott

--
-----------------------------------------
Scott Brady
http://www.scottbrady.net/
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to