Status: Untriaged Owner: [email protected] CC: [email protected], [email protected] Labels: Type-Bug Pri-2 OS-All Area-BrowserBackend
New 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 The cookies sent by a HttpNetworkTransaction is determined by request_info- >extra_headers, which is populated during URLRequestHttpJob::Start() by URLRequestHttpJobAddExtraHeaders(). So when a transaction is restarted by URLRequestHttpJob::SetAuth(), it will continue to use the previously constructed cookie header. Yet it is possible that the triggering 401 wrote cookies, so the cookies should be re-gotten each restart. -- 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 -~----------~----~----~----~------~----~------~--~---
