Re: Issue 64106 in chromium: HTTP 401 Unauthorized response using Basic authentication does not generate a new login dialog box
chro...@googlecode.com
Comment #2 on issue 64106 by cben...@chromium.org: HTTP 401 Unauthorized
response using Basic authentication does not generate a new login dialog box
http://code.google.com/p/chromium/issues/detail?id=64106
Please correct my misunderstanding - here is what I expect that Chrome did.
The initial request goes up, a 401 is returned, and the user is prompted
for username/password.
The correct username/password are entered, Chrome sends a new GET request
up with the correct Authorize headers, a 200 is returned, and Chrome caches
the username/password.
15 minutes later, the user reloads the page. We issue a GET request using
the cached username/password headers. Since the session cookie has expired,
the server returns a 401, which should be treated like a reject of the
cached credentials and the username/password prompt is presented.
It sounds like the last paragraph may not have happened. Do you know if the
request actually went out over the network instead of being served from
cache? One way to report is to start Chrome, open chrome://net-internals,
redo the behavior, and then copy-and-paste the results here. Or, use
tcpdump/wireshark/etc. to see what's happening.
chro...@googlecode.com
Status: Duplicate
Mergedinto: 72589
Comment #4 on issue 64106 by asa...@chromium.org: HTTP 401 Unauthorized
response using Basic authentication does not generate a new login dialog box
http://code.google.com/p/chromium/issues/detail?id=64106
(No comment was entered for this change.)