> Guys, that's exactly what the SID predefined constant is for -- it's defined
> only when a session is active, and it has the value
> = (e.g. PHPSESSID=1afd764ecb938274) if and only if
> the session id was passed in the URL -- otherwise it contains the empty
> string. So you can safely do:
>
> h
on 03/06/03 9:43 PM, Ford, Mike [LSS] ([EMAIL PROTECTED])
wrote:
>> -Original Message-
>> From: Justin French [mailto:[EMAIL PROTECTED]
>> Sent: 03 June 2003 06:34
>> To: Monty; [EMAIL PROTECTED]
>> Subject: Re: [PHP] Cookies and Se
> -Original Message-
> From: Justin French [mailto:[EMAIL PROTECTED]
> Sent: 03 June 2003 06:34
> To: Monty; [EMAIL PROTECTED]
> Subject: Re: [PHP] Cookies and Sessions: What's the Best Recipe?
>
>
> H,
>
> Theory only here:
>
> If there
H,
Theory only here:
If there is a GET value of PHPSESSID (or whatever your sessions are named),
then the user is more than likely taking advantage of trans-sid (sid's in
the URLs), and cookies are not available.
So, we only want to append the sid to URLs in a redirect IF the sid is found
in
>> I have a member site that uses sessions. People who have their browser
>> cookies turned off, however, cannot use our site. I read somewhere that to
>> avoid this, I'd have to manually append the PHPSESSID var to every URL when
>> redirecting in a script.
>
> One way around this would be to wri
on 01/06/03 6:01 AM, Monty ([EMAIL PROTECTED]) wrote:
> I have a member site that uses sessions. People who have their browser
> cookies turned off, however, cannot use our site. I read somewhere that to
> avoid this, I'd have to manually append the PHPSESSID var to every URL when
> redirecting in
6 matches
Mail list logo
