That's the culprit all right. And worse, it doesn't seem to be an arbitrary
browser setting but an RFC convention for HTTP 1.1 - 2 connection limit to
any server. According to Microsoft, changing it for IE even requires a
registry hack.
Thanks very much to all who contributed to this, and abo
David Hall wrote:
> Albert wrote:
>
> > same server at the same time. Don't know where to change it in Mozilla.
> >
> >
>
> type about:config in browser window
> network.http.max-persistent-connections-per-server in the line
> the default value is 2, so I think that's our answer
Yes it resolved
Albert wrote:
same server at the same time. Don't know where to change it in Mozilla.
type about:config in browser window
network.http.max-persistent-connections-per-server in the line
the default value is 2, so I think that's our answer
David Hall
--
PHP General Mailing List (http://www.p
Ron Rudman wrote:
> The log makes it look like *all* the frames are held back. Seems like the
> request is logged when it completes, so the logging process can't show us
> whether the client held back frame 3 or frame 3 was put on hold by the
> server.
I checked my logs and it seems the same. But
AM
To: PHP Superman
Cc: Ron Rudman; php-general@lists.php.net
Subject: Re: [PHP] PHP interference in frames
PHP Superman wrote:
> I'm taking a wild guess here, maybe the browser insists on waiting for
> some content but it's maximum content wait time is 5 seconds, the
> brows
> On 12/22/05, Ron Rudman <[EMAIL PROTECTED]> wrote:
>
>>I've got this down to a bare bones test but am still stumped. Can anyone
>>explain why I get the behavior I do?
>>
>>I have a frameset with 3 frames:
>>
>>testing
>>
>>
>>
>>
>>
>>
>>
>>test1.php and test2.php are both simply:
PHP Superman wrote:
I'm taking a wild guess here, maybe the browser insists on waiting for some
content but it's maximum content wait time is 5 seconds, the browser could
detect the connection to the server is still open and wait for 5 seconds or
another time
to get an idea of what the browser
I'm taking a wild guess here, maybe the browser insists on waiting for some
content but it's maximum content wait time is 5 seconds, the browser could
detect the connection to the server is still open and wait for 5 seconds or
another time
On 12/22/05, Ron Rudman <[EMAIL PROTECTED]> wrote:
>
> I'v
8 matches
Mail list logo