Comment #70 on issue 16367 by willc...@chromium.org: some http requests take many seconds or minutes http://code.google.com/p/chromium/issues/detail?id=16367
There's definitely some issue with croftjd's wireshark dump. It appears that first we GET /, and that subsequently leads to GET'ing /css/colors.css and /css/reset.css. We finish up all these requests, after which the server closes its side of the TCP connection. After a 5-6 second delay, chrome closes its side of the TCP connections for all except the connection that serviced the GET for /css/colors.css. The network sits idle for about 40 seconds, and then it starts opening new TCP connections and starts with GET /, and then subsequently GETs the rest of the page. I presume the user waited 40 seconds or so and then refreshed, after which it started working. croftjd, can you confirm? If so, then it's clear that there's a chrome bug somewhere, but without net-internals, I cannot say for sure that it's the chrome network stack at fault here or a bug somewhere else. -- 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 -~----------~----~----~----~------~----~------~--~---
