Well that must mean that they are using session_name() and session_id().  I 
really don't know why they are using that (considering it'll add 
unnecessary overhead of calling session_name(),session_id() twice).  My 
guess is that they don't have a clue about the SID constant that 
automatically gets generated as "PHPSESSIONID=dsfgsdgsdfgsgsdfg" if the 
browser does not accept cookies and is empty otherwise.  I bet they are a 
bunch of asp developers ;-)


At 03:39 PM 5/29/2002 +0200, Nick Wilson wrote:
>Hash: SHA1
>* and then Ed Gorski declared....
> > 1. This is done for users that don't use cookies.  Believe it or not but
> > there are people out there that are afraid of cookies and automatically
> > turn them off.  Without  appending the sessionid to the end of the URL,
> > sessions won't work for these people.  Now how does your host append to
> > the end of each URL?  Do they do it manually in the code or do they use
> > the SID?  An easy way to test for this is to fire up a browser with
> > cookies enabled and see if the sessionid gets appended to  each url.  If
> > so tell them to use the SID constant.  Let me know and I can help you
> > further....
>Thanks ed, I knew most of that.
>My browser has cookies *on* and I see PHPSESSID=sdkfldsdslkj in the urls
>and <input type="hidden" value="slkfsdkldsfjkldsfklj"> in my markup.
>Does that help?
>- --
>Nick Wilson     // www.tioka.com
>Version: GnuPG v1.0.6 (GNU/Linux)
>PHP General Mailing List (http://www.php.net/)
>To unsubscribe, visit: http://www.php.net/unsub.php

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to