Published by


Brink's Avatar
Administrator

Posts: 18,198

Show Printable Version 


How to Allow or Block Cookies in Google Chrome in Windows

information   Information
Cookies are small files that websites put on your PC to store information about you and your preferences. Cookies can make your browsing experience better by letting sites remember your preferences or letting you avoid signing in each time you visit certain sites. Cookies can also help a website remember your location, so it can provide you with locally relevant content, like weather. However, some cookies might put your privacy at risk by tracking sites that you visit.

All cookies are allowed by default in Google Chrome, but you can adjust this setting to allow or block cookies for all sites and set exceptions for specific sites.

This tutorial will show you how to allow or block cookies in Google Chrome for your account in Windows 7, Windows 8, and Windows 10.

Note   Note
Types of Cookies:

Session cookie

A session cookie, also known as an in-memory cookie or transient cookie, exists only in temporary memory while the user navigates the website. Web browsers normally delete session cookies when the user closes the browser. Unlike other cookies, session cookies do not have an expiration date assigned to them, which is how the browser knows to treat them as session cookies.

Persistent cookie

Instead of expiring when the web browser is closed as session cookies do, persistent cookies expire at a specific date or after a specific length of time. This means that, for the cookie's entire lifespan (which can be as long or as short as its creators want), its information will be transmitted to the server every time the user visits the website that it belongs to, or every time the user views a resource belonging to that website from another website (such as an advertisement).

For this reason, persistent cookies are sometimes referred to as tracking cookies because they can be used by advertisers to record information about a user's web browsing habits over an extended period of time. However, they are also used for "legitimate" reasons as well, such as keeping a user logged into her email account so she does not have to enter her login credentials every time she opens her browser.

Secure cookie

A secure cookie can only be transmitted over an encrypted connection (i.e. HTTPS). This makes the cookie less likely to be exposed to cookie theft via eavesdropping.

HttpOnly cookie

HttpOnly cookies can only be used when transmitted via HTTP (or HTTPS). They are not accessible through non-HTTP APIs such as JavaScript. This restriction mitigates, but does not eliminate, the threat of session cookie theft via cross-site scripting (XSS). HttpOnly cookies are supported by most modern browsers.

First-party cookie

First-party cookies belong to the same domain shown in the web browser's address bar.

Third-party cookie

Third-party cookies belong to domains different from the one shown in the address bar. These sorts of cookies typically appear when web pages feature content, such as banner advertisements, from external websites. This opens up the potential for tracking the user's browsing history, and is often used by advertisers in an effort to serve relevant advertisements to each user.

As an example, suppose a user visits Example Domain. This web site contains an advertisement from ad.foxytracking.com, which, when downloaded, sets a cookie belonging to the advertisements's domain (ad.foxytracking.com). Then, the user visits another website, Foo.com, which also contains an advertisement from ad.foxytracking.com/, and which also sets a cookie belonging to that domain (ad.foxytracking.com). Eventually, both of these cookies will be sent to the advertiser when loading their advertisements or visiting their website. The advertiser can then use these cookies to build up a browsing history of the user across all the websites that have ads from this advertiser.

As of 2014, some websites were setting cookies readable for over 100 third-party domains. On average, a single website was setting 10 cookies, with a maximum number of cookies (first- and third-party) reaching over 800.

Most modern web browsers contain privacy settings that can block third-party cookies.

Supercookie

A "supercookie" is a cookie with an origin of a Top-Level Domain (such as .com) or a Public Suffix (such as .co.uk). Ordinary cookies, by contrast, have an origin of a specific domain name, such as example.com.

Supercookies can be a potential security concern and are therefore often blocked by web browsers. If unblocked by the client computer, an attacker in control of a malicious website could set a supercookie and potentially disrupt or impersonate legitimate user requests to another website that shares the same Top-Level Domain or Public Suffix as the malicious website. For example, a supercookie with an origin of .com, could maliciously affect a request made to example.com, even if the cookie did not originate from example.com. This can be used to fake logins or change user information.

The Public Suffix List helps to mitigate the risk that supercookies pose. The Public Suffix List is a cross-vendor initiative that aims to provide an accurate and up-to-date list of domain name suffixes. Older versions of browsers may not have an up-to-date list, and will therefore be vulnerable to supercookies from certain domains.

Supercookie (other uses)

The term "supercookie" is sometimes used for tracking technologies that do not rely on HTTP cookies. Two such "supercookie" mechanisms were found on Microsoft websites in August 2011: cookie syncing that respawned MUID (Machine Unique IDentifier) cookies, and ETag cookies. Due to media attention, Microsoft later disabled this code.

Zombie cookie

Zombie cookies are cookies that are automatically recreated after being deleted. This is accomplished with the help of a client-side script. The script starts by storing the cookie's content in multiple locations, such as Flash local storage, HTML5 storage, and other client-side storage locations. When the script detects the cookie's absence, it recreates the cookie using the data stored in these locations.



Here's How:

1. Open Google Chrome.
2. Click/tap on the Customize and control Google Chrome (More) Name:  More.png
Views: 67
Size:  115 Bytes. button, and click/tap on Settings. (see screenshot below)
Note   Note
If you like, you could also enter chrome://settings/content into the address bar of Chrome, press Enter to directly open to Content settings, and go to step 5 below.


Name:  Chrome_settings.jpg
Views: 69
Size:  94.5 KB

3. Click/tap on the Show advanced settings link at the bottom. (see screenshot below)

Name:  Chrome_advanced_settings.jpg
Views: 68
Size:  79.7 KB

4. Under Privacy settings, click/tap on the Content settings button. (see screenshot below)

Name:  Chrome_cookies_settings-1.jpg
Views: 68
Size:  58.9 KB


5. Do step 6 (allow or block cookies), step 7 (add exception for site), and/or step 8 (remove exception for site) below for what you want to do. When finished, go to step 9 below.


 6. To Allow or Block Cookies for Sites in Chrome

A) Under the Cookies content settings, select the settings you want to use, and go to step 5 above. (see screenshot below)

Note   Note
To allow first-party and third-party cookies, select (dot) Allow local data to be set.

To allow first-party and third-party cookies and clear on exit, select (dot) Keep local data only until you quit your browser.

To block all cookies, select (dot) Block sites from setting any data. When you use this setting, most sites that require you to sign in won't work.

To allow only first-party cookies and block all third-party cookies, check the box next to Block third-party cookies and site data. This setting means that site data cannot be written and read, even if you've added a site to the exceptions list and have chosen to allow its cookies.


Name:  Chrome_cookies_settings-2.jpg
Views: 69
Size:  34.2 KB


 7. To Add Cookie Exceptions for Sites in Chrome

Note   Note
Without having to change your default settings in step 5, you can add an exception to the default for a specific website or domain. For example, by default, Chrome allows cookies to save local data from sites. But if you don't trust a site, you can add an exception to block cookies on only that site.


A) Under the Cookies content settings, click/tap on the Manage exceptions button. (see screenshot below)

Name:  Chrome_cookies_settings-3.jpg
Views: 70
Size:  32.7 KB

B) Under Hostname pattern, enter the site's domain name (ex: "tenforums.com"). (see screenshots below)

C) In the Behavior drop down, select to Allow, Clear on exit, or Block cookies for the site.

D) Press Enter or click/tap on a blank area to add the exception.

E) When finished adding exceptions, click/tap on the Done button, and go to step 5 above.

Name:  Chrome_cookies_settings-4.jpg
Views: 69
Size:  23.9 KB
Name:  Chrome_cookies_settings-4b.jpg
Views: 69
Size:  20.4 KB


 8. To Remove Cookie Exceptions for Sites in Chrome

A) Under the Cookies content settings, click/tap on the Manage exceptions button. (see screenshot below)

Name:  Chrome_cookies_settings-3.jpg
Views: 70
Size:  32.7 KB
B) Hover over an added exception you want to remove, and click/tap on the Delete this item Name:  Remove.png
Views: 68
Size:  153 Bytes. button to the right of it. (see screenshots below)

C) When finished removing exceptions, click/tap on the Done button, and go to step 5 above.

Name:  Chrome_cookies_settings-5.jpg
Views: 69
Size:  21.7 KB
Name:  Chrome_cookies_settings-5b.jpg
Views: 68
Size:  20.4 KB


9. When finished, click/tap on the Done button.

Name:  Done.jpg
Views: 68
Size:  47.6 KB

10. You can now close the Settings tab if you like.


That's it,
Shawn