Re: php sessions
| From: | Rob Adams | Date: | Tue, 28 Oct 2003 21:29:58 +0000 |
| Subject: | Re: php sessions | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-167941@lists.php.net to get a copy of this message | ||
"Chris Shiflett" <shiflett@php.net> wrote in message
news:20031028204548.97794.qmail@web14306.mail.yahoo.com...
> --- "CPT John W. Holmes" <holmes072000@charter.net> wrote:
> > If you are not relying on a cookie based session, then this will
> > work. Each login could be assigned a different session ID, so the
> > requests for each browser will be different because of the different
> > session IDs.
>
> What John is explaining here is that the URLs could be different if that
is how
> the session ID is propogated, thus making the requests different (they're
for
> different URLs). So, if you click a link from:
That doesn't seem to be what he's saying.
"because of the different session IDs."
It seems to me a better example of what he is saying would be:
http://example.org/foo.php?PHPSESSID=12345
vs.
http://example.org/foo.php?PHPSESSID=67890
But I was talking about cookies anyway. Which is where different browsers
have different behaviors. In IE, by default, it will not pass a cookie from
a new browser window. In Mozilla, by default, a new window keeps all the
cookies currently set. I've mostly used IE, so I've always thought that it
never passed cookies from a new browser window. Apparently, it just depends
on which browser you're using and how it is setup.
-- Rob
>
> http://example.org/foo.php?PHPSESSID=12345
>
> it could be for:
>
> http://example.org/bar.php?PHPSESSID=12345
>
> Hope that helps.
>
> Chris
>
> =====
> My Blog
> http://shiflett.org/
> HTTP Developer's Handbook
> http://httphandbook.org/
> RAMP Training Courses
> http://www.nyphp.org/ramp