Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block/allow cookies based on cookie name #80

Open
juhiyu opened this issue Jun 8, 2016 · 3 comments
Open

Block/allow cookies based on cookie name #80

juhiyu opened this issue Jun 8, 2016 · 3 comments

Comments

@juhiyu
Copy link

juhiyu commented Jun 8, 2016

Hellos, I am not sure if this but I would like to ask if it is possible to block/allow cookies by name?

just an example to help understand:

(1) github.com - has cookie name "logged_in". currently CM+ can block all cookies from a particular site but is it possible to block only cookies with the name "logged_in" on a per site/global basis?
(2) for allow cases - is it possible to allow only a cookie named "logged_in" and block every other cookie from github.com?

@vanowm
Copy link
Owner

vanowm commented Jun 8, 2016

At the moment it's not possible, but after adding read-only routine, blocking could be possible in the future.

@vanowm
Copy link
Owner

vanowm commented Jun 20, 2016

Actually it's possible simulate blocking cookies by name using read-only feature:
set expiration to read-only and change it to current time + 10 seconds, so when cookie expired, browser will not send such cookies to website, and any attempts by website create new cookie with same name will result in instant expiration, simulating blocking cookie by name.

@juhiyu
Copy link
Author

juhiyu commented Jun 20, 2016

Good thinking. not try it yet but seems automatic way to do this may make blocking work (CM+ can insert dummy value to cookie before/as cookie is set by site and then set expired date/read-only so browser won't send it and site cannot set it again?) but i have not given it too much thought or testing. one issue i see it will be restricted only to 1 site not multiple sites/global.

method may also be viable for allow cases but I am not sure (CM+ can have certain cookie(s) set by user as allow and automatically use the expiry method to block every other cookie and actively keep searching for cookies and block before they are set by the site?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants