Posted by Pink Floyd on 10/04/30 11:10

OK, after a little more closer examination, it does
appear that the 'urlencode' is being used. I did the
encode/decode thingy. BUT, the only character that is
being messed up (at least the ones I had) appears to
be '+'.

After a lot of trial and error, I am fairly convinced
that PHP parses the Cookie before 'urldecoding' it and
for some reason the '+' character seems to be treated
special. It could be that there may be some more
'filtering' going on before it reaches the 'urldecode'
step.
Richard, thanks for being with this thread so far. I
will see if i can produce some output.


--- Richard Lynch <ceo@l-i-e.com> wrote:
>
> > Greetings,
> > I tested Richard's suggestion below, and it
> appears
> > that 'urlencode' is not the function that I want.
> > Are there any other options? Does anyone know
> what
> > PHP uses internally to 'munge' the cookie? I
> looked at
> > the php.ini doc's and I could not find any option
> to
> > turn off whatever 'encoding' PHP uses internally.
>
> Hmmm.
>
> Okay, show us some "before" and "after" values.
>
> It's *GOT* to be something not unlike urldecoding if
> it changes + to space.
>
> Damn! PHP's urlencode might use %20 instead of +
> (or vice versa) so then
> the urldecode and urlencode are not be true inverse
> functions, for
> space/%20/+ scenarios.
>
> --
> Like Music?
> http://l-i-e.com/artists.htm
>
>



__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

[Back to original message]