Let's see how the paranoid manages Cookies.

When using Web browsers, most people do not manage cookies in any form. The browser only accepts all cookies and saves them until they expire-if so. For a while, it seems that everyone is concerned about the tracing of cookies, but this time has passed.
However, some people try to manage cookies in the browser. However, for different people, the selection of cookies management policies varies greatly.

Cookies Management Policy

Reject all cookies

A simple (but inconvenient) method is to directly disable the use of all cookies. Of course, this will make it very difficult to log on to a website that requires cookies. Worse, some websites cannot be browsed normally. When you access the network logs of a custom domain name provided by WordPress.com, disabling the use of all cookies will result in this situation. The website will be loaded in an infinite loop, mainly to tell people that if all cookies are rejected, "We don't want you to access our website ."

I need to point this out. For website operations, cookies must be a poor design. This is not a good solution, and the services provided by WordPress.com are not an appropriate choice for domain name hosting. However, this does not change the fact that we have time to access the websites supported by WordPress.com, just as we log on to TechRepublic, which makes it meaningless to reject all cookies, although this approach seems the best.

Clear cookies upon exit

Another simple method is to configure the browser and clear all cookies upon exit. In this case, it will not handle bad cookies in the current browsing session. It can ensure that the information will not be obtained by cookies when you log on to the bank website after you access a website with some problems, this can lead to a dangerous situation. All you need to do is close the browser used to access the bank website, and then open the browser to access another website.

This will prevent you from logging on to some websites permanently, which will affect some people's work. Therefore, if you want to directly log on to the TechRepublic website without entering the login information every time, you can use cookies to ensure that you can directly go to the discussion.

This approach also prevents others from spying on your computer system through physical connections, especially when history information is cleared like cookies.

Privacy Mode

Now, Web browsers are beginning to provide privacy, or "camouflage" browsing mode. In this mode, the cookies and history generated by the created tag or independent browsing process are separated from those generated by the main browsing process, and are automatically cleared at the exit time. When you exit the private browser mode or tag, the browser still runs under normal configuration. The tag used is no different from the previous one. As long as you do not use the privacy mode, you can "always" login to any favorite website at any time.

In this way, you can better prevent local snoop. As long as you use the privacy mode, no cookies or historical records are available when you visit a website that you do not want others to know. At the same time, the browser cookies and the rest of the history will be properly managed.

Reject third-party cookies

Some browsers provide the ability to accept first-party cookies, but reject third-party cookies. In general, it seems a good idea to reject third-party cookies (such as scripts) in terms of security. But unfortunately, in the real world, things are not as simple as we expect. Many websites use logon cookies through different domain names. For example, when logging on to www.example.com, logging on to cookies comes from login.example.com. If you reject all third-party cookies, you can find that you cannot log on to www.example.com.

The same problem often occurs when you choose whether to accept or disable third-party JavaScript and other third-party functions, just as cross-site scripting (XSS) vulnerability attacks have tempted you to run third-party scripts.

Refined Control

Some browsers provide excellent refined control functions, which is a good choice for people who want to directly control them. However, most of the refined functions usually use automatic setting options. Firefox is a good example. You can directly manage each Cookie here, but the only control method is whether to accept the Cookie in the future. Most of the work needs to be done by users.

Conclusion

Of course, some Web browsers provide extended systems, some of which can add additional Cookie management functions to browsers. At the same time, some browsers provide fewer cookie management solutions than others. This is Google Chrome. So far, it has not provided refined control functions like the Firefox browser, which is one of the few advantages Firefox has over Chrome, if you ignore the number of Firefox extension plug-ins and the Chrome Promotion System (this is currently only a Developer Preview.

Depending on the type of browser you use, you can also provide many options. What function you choose depends on the degree of paranoia.

Of course, all these methods are useless for Flash cookies.