I use both... and the way I see PHP handling it is like this...
First call in it will add the SESSID to the hrefs.
Next call (page load) if it finds the cookie it will not append SESSID to URL.
However if it doesn't it will.
There are a few instance were I need to get the SESSION ID and append them myself.
Redirects are a good example you need to add it yourself.
header("Location: http://mysite.org/index.php?PHPSESSID=$sid";);
Cheers,
Mike
P.S. This is just from my obeservation....
*********** REPLY SEPARATOR ***********
On 03/01/2003 at 1:52 PM [EMAIL PROTECTED] wrote:
>Sorry I didn't make myself more clear. I only want to use server side
>sessions. I don't want to have to rely on a client having cookies enabled
>in their browser. So far having trans_sid is just doing the trick. I can
>save values into sessions server side and not explicitly create a client
>side cookie with any values to retrieve the information.
>
>Thanks again,
>
>Ed
>
>
>On Fri, 3 Jan 2003, Ford, Mike [LSS] wrote:
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> To: [EMAIL PROTECTED]
>>
>> Does php use cookies for sessions even if you don't explicitly use
>> cookie
>> functions to save session data server side?
>> --------------------------
>>
>> That question doesn't even make sense to me -- cookie functions can't
>save
>> data server side, for one thing! Can you try to explain exactly what it
>is
>> you're trying to find out?
>>
>> Cheers!
>>
>> Mike
>>
>
>
>--
>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
