Skip to content
This repository has been archived by the owner on Nov 15, 2017. It is now read-only.

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

Closed
gorhill opened this issue Oct 2, 2013 · 4 comments

Comments

@gorhill
Copy link
Owner

gorhill commented Oct 2, 2013

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

@gorhill
Copy link
Owner Author

gorhill commented Oct 2, 2013

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

@gorhill
Copy link
Owner Author

gorhill commented Oct 17, 2013

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 gorhill closed this as completed Oct 17, 2013
@gorhill gorhill reopened this Oct 17, 2013
@gorhill
Copy link
Owner Author

gorhill commented Oct 17, 2013

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 added a commit that referenced this issue Oct 17, 2013
@gorhill
Copy link
Owner Author

gorhill commented Oct 17, 2013

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.

@gorhill gorhill closed this as completed Oct 18, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant