On Tue, May 8, 2007 1:31 pm, [EMAIL PROTECTED] wrote:
> How does one check to see if the user's browser accepts
> session cookies?
My browser doesn't make that decision. I do. :-)
Send me one and see if it comes back.
If it does come back, use it as your cookie.
Don't send me a second cookie.
I don't think that there is a difference between session or regular cookie
acceptance.
Have a look at the 1st code example here :
http://www.php-code-search.com/?q=cookie%20support
berber
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 8
Rasmus Lerdorf wrote:
> Chris Shiflett wrote:
>
>>Rasmus Lerdorf wrote:
>>
>>
>>>Why modify my test?
>>
>>
>>Because it has less delay. Thus, it's more difficult to tell if the
>>browser is requesting the new URL before or after receiving the entire
>>response. My script is essentially the same th
Chris Shiflett wrote:
> Rasmus Lerdorf wrote:
>
>> Why modify my test?
>
>
> Because it has less delay. Thus, it's more difficult to tell if the
> browser is requesting the new URL before or after receiving the entire
> response. My script is essentially the same thing, but the script takes
> 30
Rasmus Lerdorf wrote:
Why modify my test?
Because it has less delay. Thus, it's more difficult to tell if the
browser is requesting the new URL before or after receiving the entire
response. My script is essentially the same thing, but the script takes
30 seconds to execute. It makes the dis
Chris Shiflett wrote:
> Rasmus Lerdorf wrote:
>
>> Then you have configured your server to always turn on output
>> buffering or your test script is bad.
>
>
> I don't think it's either, but I'll let you decide. I tried a new test
> with your code and some slight modifications:
Why modify my te
Rasmus Lerdorf wrote:
Then you have configured your server to always turn on output
buffering or your test script is bad.
I don't think it's either, but I'll let you decide. I tried a new test
with your code and some slight modifications:
http://www.php.net/');
$fp = fopen('/tmp/log.txt', 'w
Chris Shiflett wrote:
> Chris Shiflett wrote:
>
>> > And the browsers tend to redirect right away once they get this
>> > header.
>>
>> I would find that very surprising. Maybe I'll experiment.
>
>
> I tested this with Firefox 1.0.4, Firefox 1.0.6, and Safari 1.3. None of
> them request the new
Chris Shiflett wrote:
> And the browsers tend to redirect right away once they get this
> header.
I would find that very surprising. Maybe I'll experiment.
I tested this with Firefox 1.0.4, Firefox 1.0.6, and Safari 1.3. None of
them request the new URL before receiving the previous response
Chris Shiflett wrote:
> Rasmus Lerdorf wrote:
>
>> That's a bit misleading. The HTTP response headers are sent a soon
>> as you output something from your script (calling header() or
>> setcookie() doesn't count as output, so you can set all the headers
>> and cookies you want).
>
>
> They're se
Rasmus Lerdorf wrote:
That's a bit misleading. The HTTP response headers are sent a soon
as you output something from your script (calling header() or
setcookie() doesn't count as output, so you can set all the headers
and cookies you want).
They're sent to Apache, but that doesn't mean anyth
Rasmus Lerdorf wrote:
That's a bit misleading. The HTTP response headers are sent a soon
as you output something from your script (calling header() or
setcookie() doesn't count as output, so you can set all the headers
and cookies you want).
They're sent to Apache, but that doesn't mean anythin
Chris Shiflett wrote:
> Jasper Bryant-Greene wrote:
>
>> That is not true. The output to the client will look like this:
>>
>> HTTP/1.1 302 Found
>> Set-Cookie: name=value;domain=whatever
>> Location: http://my.domain.com/my.php
>> [...]
>
>
> Very nice explanation. :-)
>
> It is a common misco
Jasper Bryant-Greene wrote:
That is not true. The output to the client will look like this:
HTTP/1.1 302 Found
Set-Cookie: name=value;domain=whatever
Location: http://my.domain.com/my.php
[...]
Very nice explanation. :-)
It is a common misconception that header('Location: ...') redirects the
Philip Hallstrom wrote:
> Is there a way, using PHP, to determine if session cookies
> are enabled (or disabled) in the user's browser privacy
> settings?
Set a cookie using setcookie().
Then use an HTML meta refresh (or javascript, just not
Header("Location...) to redirect them to another page
TECTED]>
Cc: "php list"
Sent: Thursday, September 01, 2005 10:43 PM
Subject: Re: [PHP] session cookies
Philip Hallstrom wrote:
Then use an HTML meta refresh (or javascript, just not
Header("Location...) to redirect them to another page.
Why not header("Location...")
Mikey wrote:
Jasper Bryant-Greene wrote:
Philip Hallstrom wrote:
Then use an HTML meta refresh (or javascript, just not
Header("Location...) to redirect them to another page.
Why not header("Location...")? Just out of interest -- it's always
worked for me, and it's a much better way to r
Philip Hallstrom wrote:
Then use an HTML meta refresh (or javascript, just not Header("Location...)
to redirect them to another page.
Why not header("Location...")? Just out of interest -- it's always worked for
me, and it's a much better way to redirect users for many reasons[1] (like
not br
Jasper Bryant-Greene wrote:
Philip Hallstrom wrote:
Then use an HTML meta refresh (or javascript, just not
Header("Location...) to redirect them to another page.
Why not header("Location...")? Just out of interest -- it's always
worked for me, and it's a much better way to redirect users f
Philip Hallstrom wrote:
Then use an HTML meta refresh (or javascript, just not
Header("Location...) to redirect them to another page.
Why not header("Location...")? Just out of interest -- it's always
worked for me, and it's a much better way to redirect users for many
reasons[1] (like not br
Is there a way, using PHP, to determine if session cookies are enabled (or
disabled) in the user's browser privacy settings?
Set a cookie using setcookie().
Then use an HTML meta refresh (or javascript, just not
Header("Location...) to redirect them to another page.
On that page, see if the
On Wednesday 11 May 2005 13:26, Richard Lynch wrote:
> On Tue, May 10, 2005 7:04 pm, Kirsten said:
> > I'm using php sessions with cookies.
> > I realized that Firefox shared cookies between different instances
> > (unlike IE that when someone open a new bank window a new session is
> > created).
>
> Here's a solution: It's not a problem. It's the way it's SUPPOSED to be.
> :-)
>
> It's actually a BETTER browser because of that.
I found dozens of firefox related sites that say that this is one of the
good things IE has (like showModalDialog).
> Maybe it's just me, but it sounds to me like
On Wednesday 11 May 2005 05:04, Kirsten wrote:
> I'm using php sessions with cookies.
> I realized that Firefox shared cookies between different instances (unlike
> IE that when someone open a new bank window a new session is created).
>
> Has anyone found a solution to this problem? Maybe detectin
On Tue, May 10, 2005 7:04 pm, Kirsten said:
> I'm using php sessions with cookies.
> I realized that Firefox shared cookies between different instances (unlike
> IE that when someone open a new bank window a new session is created).
That's because IE stupidly creates a whole new program/process on
> Jeff Bluemel wrote:
>
> >I want to force it to use a cookie that points to a transparent SID on
> >my system.
> >
>
> Can you elaborate on this? I have no idea what you mean.
for some reason when I was reading the documentation on sessions on php.net
I thought it stated that it was possible to
I also just noticed that you have session.use_only_cookies = 1, so
unless you get the session ID back in a cookie, the session will restart.
Chris Shiflett wrote:
>> I've got the following options in my php.ini, but the system doesn't
>> seem to
>> ever use a cookie, and the sessions don't die
Jeff Bluemel wrote:
>I want to force it to use a cookie that points to a transparent SID on
>my system.
>
Can you elaborate on this? I have no idea what you mean.
>I've got the following options in my php.ini, but the system doesn't seem to
>ever use a cookie, and the sessions don't die. (that
Start by adding a "session_start()" to the 2nd file, then see what happens.
Kirk
> Hi again, I am doing a simple example of cookies and my
> server seems to
> get frozen.
>
> Basically, what I do is:
>
> file01.php:
> session_start();
> seession_register("sess_var");
> sess_var = "Hello";
(responding to myself)
In article <93uoh9$613$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
(CC Zona) wrote:
> This must sound pretty far-fetched, but as far as I can tell, my site is
> attempting to set a session cookie from any and all PHP pages, even when
> the page has no calls to session_* funct
30 matches
Mail list logo
