Ensure chromium is visually in sync with HTTPSB regarding blocked/allowed cookies

[gorhill]

As discussed in #8. Cookies are really blocked by HTTPSB, it's just that chromium need to be told about it.

[gorhill]

It's just a matter of calling findAndRecordCookies for all cookies found sitting in the browser at launch time.

[gorhill]

Wont fix. That chromium UI is not in sync with HTTPSB internals is normal, given that chromium UI to manage white/blacklist for cookies, scripts, plugins has no precedence over an extension.

Requesting that chromium UI is in sync with a third-party extension would require an unacceptable overhead for extensions, i.e. in the current case, walk through all cookies sittings in the browser's store and telling the browser whether each domain should be blacklisted or whitelisted.

So it is a case of whether the user trust the extension is doing what it says it is doing, the same way the user has to trust chromium is doing what chromium says it is doing. The important part here is that if you installed HTTPSB, it is to replace chromium's own minimal UI to deal with white/blacklists, not as a mere sidekick.

[gorhill]

Ok, for now I decided HTTP Switchboard will neither expressly allow or block cookies, the control is in the hand of the user. However the behavior of HTTPSB regarding how it handles the cookies themselves stays the same: all outgoing blacklisted cookies are removed from the headers, so whoever created the cookie will never hear back about it.

[gorhill]

A note: not blocking cookies allow a more accurate reporting of attempted cookie usage by web sites. Better know what they are trying to do and prevent it, than being misled by thinking they are not using any cookies.