Clear the HTTP auth state when clearing cookies or cache.

chrome/browser/profiles/profile_impl_io_data.cc

Index: chrome/browser/profiles/profile_impl_io_data.cc
diff --git a/chrome/browser/profiles/profile_impl_io_data.cc b/chrome/browser/profiles/profile_impl_io_data.cc
index 6a68c08b8c0851fffb3f17d96fceb2aa496c40ff..67cee9afb4ba924ca7576936bdefa4c37678e462 100644
--- a/chrome/browser/profiles/profile_impl_io_data.cc
+++ b/chrome/browser/profiles/profile_impl_io_data.cc
@@ -784,9 +784,13 @@ void ProfileImplIOData::ClearNetworkingHistorySinceOnIOThread(
   DCHECK_CURRENTLY_ON(BrowserThread::IO);
   DCHECK(initialized());
 
+  // Synchronous deletion.
   DCHECK(transport_security_state());
-  // Completes synchronously.
   transport_security_state()->DeleteAllDynamicDataSince(time);
+  DCHECK(http_network_session_.get());
+  http_network_session_->http_auth_cache()->Clear();

[mmenke, 2015/12/01 15:59:48]

I don't think it makes much sense to clear auth information without also
flushing the socket pools.  Otherwise, we may still have reusable connections
around that actually use that information.

[msramek, 2015/12/01 16:26:04]

Ok, I'll look into it! (I'm not very familiar with our network stack)

[asanka, 2015/12/01 17:51:10]

Also, this is meant to delete state since |time|. HttpAuthCache already keeps
creation timestamps around for cache entries which we should use to only remove
entries that were created after |time|.

+
+  // Asynchronous deletion, calls the |completion| callback when finished.
   DCHECK(http_server_properties_manager_);
   http_server_properties_manager_->Clear(completion);
 }