Add support for clearing the HTTP auth cache.

Add support for clearing the HTTP auth cache.

This patch adds an API so that the platform can clear the HTTP auth cache
at will. This can be useful when clearing private browsing data to prevent
cached credentials from being re-used.

BUG=63723
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=282944

[christiank, 2014-06-24 09:06:26]

Hi,

I'd like to clear any cached credentials in the auth cache when clearing the
users private data. Since I couldn't find any API to do this I added one.

What do you think?

Thanks!

Regards,
Christian

[eroman, 2014-07-08 01:35:14]

Where is this new call used from?

I imagine you need to also add some callsite to browsing_data_remover.cc.

Lastly, please link to a bug for the feature

[christiank, 2014-07-08 11:01:50]

On 2014/07/08 01:35:14, eroman wrote:
> Where is this new call used from?
> 
> I imagine you need to also add some callsite to browsing_data_remover.cc.
> 
> Lastly, please link to a bug for the feature

We (Opera) is currently calling it from our own data remover on the "content"
side (our implementation of content). We're not using browsing_data_remover.cc
or anything else from chrome/ in general. If you think this patch is of interest
to Chrome I'll see if I can expose it to browsing_data_remover.cc somehow.
Currently the chain of calls looks roughly like this:
GetURLRequestContext()->http_transaction_factory()->GetSession()->http_auth_cache()->Clear();

I have now created a bug. Unforutnately I don't have bug editing permissions yet
so I had to go through the wizard.

[asanka, 2014-07-11 21:55:41]

On 2014/07/08 11:01:50, christiank wrote:
> On 2014/07/08 01:35:14, eroman wrote:
> > Where is this new call used from?
> > 
> > I imagine you need to also add some callsite to browsing_data_remover.cc.
> > 
> > Lastly, please link to a bug for the feature
> 
> We (Opera) is currently calling it from our own data remover on the "content"
> side (our implementation of content). We're not using browsing_data_remover.cc
> or anything else from chrome/ in general. If you think this patch is of
interest
> to Chrome I'll see if I can expose it to browsing_data_remover.cc somehow.
> Currently the chain of calls looks roughly like this:
>
GetURLRequestContext()->http_transaction_factory()->GetSession()->http_auth_cache()->Clear();
> 
> I have now created a bug. Unforutnately I don't have bug editing permissions
yet
> so I had to go through the wizard.

I've merged the bug over to the canonical issue at
https://code.google.com/p/chromium/issues/detail?id=63723.

For Chromium, this code will need to invoked from browsing_data_remover.cc.
That'll also need to respect the scope of the browsing data removal. I.e. if the
user is removing browsing data within a time period, this should only remove
HttpAuthCache entries created during that time period.

[eroman, 2014-07-11 22:49:34]

LGTM for Opera's use.

[christiank, 2014-07-14 12:23:23]

The CQ bit was checked by christiank@opera.com

[commit-bot: I haz the power, 2014-07-14 12:24:26]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/christiank@opera.com/351833002/1

[commit-bot: I haz the power, 2014-07-14 14:23:51]

Change committed as 282944