Re: [PHP] URLencode issues - halp! - code included

2003-01-24 Thread Marek Kilimajer
on the browser? Thanks, -Mike -Original Message- From: David T-G [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 3:31 PM To: PHP General list Cc: SpyProductions Support Team Subject: Re: [PHP] URLencode issues - halp! Mike -- ...and then SpyProductions Support Team

Re: [PHP] URLencode issues - halp!

2003-01-24 Thread Ernest E Vogelsinger
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 %

[PHP] URLencode issues - halp!

2003-01-23 Thread SpyProductions Support Team
I am having some issues, apparently, with URL encode. I've got people signing up for a membership on a site, but some of their memberships fail because the username, which in encoded, sometimes goes through fine and sometimes does not. Are there any special reasons this may happen? I decided

Re: [PHP] URLencode issues - halp!

2003-01-23 Thread rw
Some code please! RW Quoting SpyProductions Support Team [EMAIL PROTECTED]: ### ### I am having some issues, apparently, with URL encode. ### ### I've got people signing up for a membership on a site, but some of their ### memberships fail because the username, which in encoded, sometimes

Re: [PHP] URLencode issues - halp!

2003-01-23 Thread Chris Shiflett
--- SpyProductions Support Team [EMAIL PROTECTED] wrote: I am having some issues, apparently, with URL encode. ... Oh, and BTW, I do use urldecode(). :) If you are using URL encode in order to pass values on the URL (and then reference them as $_GET['blah']), then URL decoding is superfluous

Re: [PHP] URLencode issues - halp!

2003-01-23 Thread David T-G
Mike -- ...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

RE: [PHP] URLencode issues - halp! - code included

2003-01-23 Thread SpyProductions Support Team
:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 3:31 PM To: PHP General list Cc: SpyProductions Support Team Subject: Re: [PHP] URLencode issues - halp! Mike -- ...and then SpyProductions Support Team said... % % I am having some issues, apparently, with URL encode. ... % % I decided

Re: [PHP] URLencode issues - halp! - code included

2003-01-23 Thread Leif K-Brooks
: SpyProductions Support Team Subject: Re: [PHP] URLencode issues - halp! Mike -- ...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

RE: [PHP] URLencode issues - halp! - code included

2003-01-23 Thread SpyProductions Support Team
So what is the decode part for then? Earlier versions of PHP? :) Thanks, -Mike -Original Message- From: Leif K-Brooks [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 4:43 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [PHP] URLencode issues - halp

RE: [PHP] URLencode issues - halp! - code included

2003-01-23 Thread Chris Shiflett
--- SpyProductions Support Team [EMAIL PROTECTED] wrote: So what is the decode part for then? Earlier versions of PHP? No, it is for decoding URL-encoded strings, just as you would expect. The reason you do not need to decode URL variables is because they are not URL-encoded by the time your