Greetings again,
Thanks to richard for pointing out a good way to
devle
into the source. It appears after browsing through the
source that the ' ' (space) is encoded to '+'. Also
the
characters '_', '-', '.' do get special treatment.
Obviously, this works great in the scenario where the
cookie is
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 Cook
ng for what-ever php uses or even better to
turn it off?
Thanks
MK
--- Pink Floyd <[EMAIL PROTECTED]> wrote:
> Richard,
> Thanks for clearing that up. I figured the value
> was
> transformed by the parser, but I did not know that
> it
> could be urlencode. I will test it
AIL PROTECTED]> wrote:
> Pink Floyd wrote:
> > (I had posted this in the Zend php-general mailing
> > list
> > but it did not show up in php.net, so here it is
> > again)
> > Greetings,
> > I am not sure whether this is a bug or a 'feature'
> >
(I had posted this in the Zend php-general mailing
list
but it did not show up in php.net, so here it is
again)
Greetings,
I am not sure whether this is a bug or a 'feature'
(new to PHP). I have a cookie that is set by our
password server (NON-PHP) for our domain, whose value
is base64 encoded when
5 matches
Mail list logo
