Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 8253 by Gregor.Kuhlmann: Chrome stalls when accessing website
with HTTP basic auth, freezes complete WIndows network stack
http://code.google.com/p/chromium/issues/detail?id=8253
Chrome Version : 1.0.154.48
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 3: OK
Firefox 3: OK
IE 7: OK
What steps will reproduce the problem?
Visit a website with HTTP basic authentication and lots (~90) of embedded
images.
What is the expected result?
The page is displayed after the user enters his credentials (or just
confirms the saved username and password).
What happens instead?
The requested page is loaded (from what I can see in the webserver logs),
but then all transfers appear to stall, and all TCP connections on the
computer running Chrome are broken.
Logging the requests with the Fiddler tool indicates that all the images
are first requested without the authentication header, and only after the
server responds with a 401 error, the request is repeated with the proper
authentication header.
It appears to be a timing problem, because when fiddler is running the page
loads completely, also if Chrome is run in a VM. Apparently the large
number of responses during a short period of time causes Windows' TCP stack
to break down.
--
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
-~----------~----~----~----~------~----~------~--~---
