Comment #45 on issue 16367 by [email protected]: some http requests take  
many seconds or minutes
http://code.google.com/p/chromium/issues/detail?id=16367

Here is one possible explanation which fits the data, but isn't fully  
satisfying as it depends on weird server configuration:

In the HTTP response I noticed the server specifies a timeout in the  
keep-alive header:

     Keep-Alive: timeout=15, max=???

(I forget the exact value of max, but it doesn't really matter for the sake  
of my argument, since neither Chrome nor Firefox respect it).

Fact:
Chromium DOES NOT respect timeout= argument in Keep-Alive headers.

Fact:
Firefox DOES respect the timeout= argument in Keep-Alive.

So what does this mean?

Well, if we had been running in Firefox it would have never hit this  
problem.
After 15 seconds it would have closed the connection (respecting the  
timeout= parameter), and so at t=146 we would have opened a fresh
connection to the server and things are peachy.

Whereas on Chromium, after 146 seconds we still have the same socket open,  
and we now try using it, and for whatever reason the server doesn't
respond.

Supposition:
Maybe developer.apple.com has some optimization / DDOS protection or  
whatever, which gives it a tendency to hose TCP connections after the
timeout has expired. [This is the unsatisfying part of my argument, but is  
at least testable].

We could further postulate that this only "reproduces" on Mac because it is  
mostly Mac users that are browsing developer.apple.com.

Regardless of what the problem actually is, respecting the timeout would  
have fixed it in this case (possibly papering over some other bug).


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to