Status: Unconfirmed
Owner: [email protected]
Labels: Type-Bug Pri-2 OS-All Area-Misc

New issue 6166 by cybrmatt: ERR_EMPTY_RESPONSE when authenticating to  
linksys
http://code.google.com/p/chromium/issues/detail?id=6166

Chrome Version       : 2.0.156.1
Other browsers tested:
   Add OK or FAIL after other browsers where you have tested this issue:
      Safari 3:
     Firefox 3: OK
          IE 7: OK

I connect to a linksys router at home.  Prior to the new dev release, I
couldn't use chrome to authenticate to it because it had a blank username
for authorization.  I can now connect, but the initial connection (which
uses https) errors out and has to be retried, which then works.  The steps
below will hopefully clarify what I mean by this.

What steps will reproduce the problem?
1. Open a new tab & go to the admin interface url (https://a.b.c.d)
2. Get presented with "The site's security certificate is not trusted!"
because it uses a self-signed cert.
3. Click "Proceed Anyway"
4. On a normal webpage, this brings up the auth box.  Here, it instead
throws Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error.
5. If I go back to the URL bar and hit "enter" again, to reload the page,
the authentication box now appears.  I can log in and the web interface
loads.

What is the expected result?
It is expected that after accepting the certificate the browser will
request authentication and load the page automatically.

What happens instead?
It immediately presents an error page after confirming the cert.  Upon re-
submitting the same URL, the page then authenticates and loads properly, as
if it had connected the first time.

Please provide any additional information below. Attach a screenshot if
possible.
This does not seem to occur on other sites which use self-signed certs, so
it seems to be unique to the linksys (at this point in time anyway).  The
only historical difference with the linksys was the use of a blank
username, which is new in this chrome release.  Note that I have not tested
this on a wide variety of sites, so the username could be the key, but
could also be coincidental.  This is 100% reproducible on my linksys.


--
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