Issue 1863: Chrome has problems with Linksys embedded device web pages
http://code.google.com/p/chromium/issues/detail?id=1863
Comment #11 by [EMAIL PROTECTED]:
Using the Fiddler 2 web debugger, I found that the transaction that fails
is an HTTP POST, and the reason we get net::ERR_INVALID_RESPONSE is that
the server closes the connection without sending any response.
A noticeable difference between Google Chrome's and IE's request headers
for the POST is that IE sends a preemptive Authorization header but Google
Chrome doesn't. I suspect this is why the embedded HTTP server in the
Linksys router doesn't like Google Chrome's POST request and closes the
connection. If so, this bug isn't a WinHTTP bug but rather our not
implementing preemptive authentication.
Darin, is there a problem for a server to respond with 401 to a POST
request without an Authorization header? I'm wondering why the embedded
HTTP server doesn't do that. (It identifies itself as "Server: httpd".)
Eric, have you checked in your preemptive authentication changelist on
the trunk?
Issue attribute updates:
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
--
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
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
