Comment #1 on issue 6450 by [email protected]: Cookies set during a 401 are not applied to the restarted transaction http://code.google.com/p/chromium/issues/detail?id=6450
See http://code.google.com/p/chromium/issues/detail?id=1629#c17 for an example where this occurs. In chromium we get caught in an infinite loop (keep getting 401 challenge). The server expects the cookie "sessionid=X", but we will keep sending the old "sessionid=signedoff". (In other words, we keep repeating "Transaction 2"). --- Transaction 1 --- GET /login HTTP/1.1 Cookie: sessionid=signedoff HTTP/1.1 401 Unauthorized Set-Cookie: sessionid=X; path=/ WWW-Authenticate: Digest ... --- Transaction 2 --- GET /login HTTP/1.1 Authorization: Digest username=.... Cookie: sessionid=signedoff HTTP/1.1 401 Unauthorized Set-Cookie: sessionid=X; path=/ WWW-Authenticate: Digest ... -- 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 -~----------~----~----~----~------~----~------~--~---
