At 22:30 23.01.2003, David T-G spoke out and said:
--------------------[snip]--------------------
>...and then SpyProductions Support Team said...
>%
>% I am having some issues, apparently, with URL encode.
>...
>%
>% I decided to use this because people are allowed to use *any* key as part of
>% their name, so a name like "rt'$%^*&'rt" is perfectly allowable.
>
>
>Makes sense, but I'd use base64_encode (with base64_decode, of course)
>rather than urlencode; it will properly shield everything. No, I don't
>know why 'normal' names fail and goofy ones don't; without some code and
>some specific examples we can't really tell too well :-)
--------------------[snip]--------------------
I believe you could even use md5() to "encode" the logon... would shield
everything too :)
--
>O Ernest E. Vogelsinger
(\) ICQ #13394035
^ http://www.vogelsinger.at/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
