Anonymity in Human Emulator Studio. Cookies, cache and more.

Browser cache.

What is the Browser Cache?

In fact, the cache is a bunch of temporary files downloaded from the site when you first go to it, provided that caching is enabled on it. This technology is used to speed up work with the site, that is, the included cache on the site reduces the latency of downloading and displaying content and reduces network traffic.

Anonymity and cache.

But at the same time, saving such files carries certain risks, including third-party software that can get access to these files. In addition, the sites themselves can put special files in the cache for your subsequent identification. Therefore, to maintain your anonymity, the cache must be cleaned.

Human Emulator Studio uses the object browser command clear_cache to clear the cache.

php example:

At the same time, data from local storage or local data storages are also cleaned with this function.

Web storage.

Web storage (or earlier DOM Storage) https://html.spec.whatwg.org/multipage/webstorage.html is an HTML standard that provides functionality for storing data on the client side during a session (Session Storage), or after the end of the session (Local Storage). The standard Web storage appeared when the owner of the sites stopped grabbing traditional cookies as they had significant size limitations and security problems.

DOM Storage is the name for a set of tools related to storage, first introduced in the Web Applications 1.0 specification, and now singled out as a separate W3C Web Storage specification.

Accordingly, for your anonymity, these repositories must also be cleaned. If you need to clean only Local Storage, you can use the object browser command clear_local_storage.

php example:

php example:

IndexedDB.

Another user data storage. Since version 7.0.42, it is cleaned using the object browser command clear_cookies.

And also a separate function was added to the object browser clear_indexed_db, only for cleaning this storage.

php example:

Cookies(HTTP cookies, Flash Cookies, Evercookies).

Http cookies (web cookies) – this is data from the server, which in text form stores on your computer various settings, authentications, sessions, statistics, personal preferences, etc.

Cleaned using the object browser command clear_cookies($match_name,$clear_session=false,$clear_flash=true);

match_name – a template for searching sites whose cookies need to be cleared (part of the address), if an empty string is specified – all are cleared;
clear_session – clear session cookies (true) or do not clear (false) when the command is executed. Session cookies – tracking the status of a user’s access session;
clear_flash – whether to clear (true) or not to clear (false) flash cookies.

Flash Cookies (LSO Cookies) – unlike ordinary cookies, they are common to all browsers and with their help you can store a larger amount of information. These cookies are also cleared using the object browser command clear_cookies.

This function clears all cookies, including flash cookies.

In addition to cleaning with the command clear_cookies for Flash Cookies, it is possible to delete them with the object browser command flash_cookies_delete, and also restore the saved flash cookies from the specified folder as current ones using command of the object browser flash_cookies_restore and save the current flash cookies to the specified folder using the object browser command flash_cookies_save.

php example:

Evercookie — the most stable cookies, cookies are stored in almost all available storages and if they are not cleared from everywhere, they are automatically restored from the remaining ones. To clear them, you need to close all the tabs, go to the remaining page on a blank page and clean the cookies and cache and preferably restart the program.

php example:

Saving and restoring cookies and cache.

In order to save and then reuse all cookies and cache, you can use the functions of the object browser
set_cookies_folder – set a folder for cookies. Cache folders will be created inside the specified folder with cookies.

The logic here is simple: you set a new folder and perform all the necessary actions such as navigating the site, logging into the account, downloading content, etc., then change the folder to a new one and again perform all the necessary actions under a different account. As a result, you will have several folders with cookies and cache, which can be used in the future.

php example:

Please note that when you restart the program, the folders with cookies are reset on the default path, so if you want the folder with cookies to remain the same after restarting the program, you need to use the object app command restart to restart program and in it set the desired folder with cookies. The cache folder is now always inside the cookie folder.

Deleting folders with cookies and cache at the time of starting the program.

In the program from version 7.0.25, settings have appeared for clearing cookies and cache at startup. Since it is not possible to completely delete the folders with cookies and the cache while the program is running, special settings have been added so that at the time the program starts, these folders are not already occupied by the browser processes to completely delete them. These settings are in the program settings tab “General” checkboxes “Clear cookies of the current port by start” and “Clear cache of the current port by start“.

Complete cleaning.

Complete cleaning of everything can be done using the command clear of the object app

php example:

To completely clear all cookies and cache, after clearing them, you must restart the program using the object app command restart. This command allows you to restart the program with the launch of the script, as well as set a number of settings such as port, path to the folder with cookies. In addition, when the program is completely restarted, the memory leaks will also be cleaned, and if you have the settings “Clear cookies on the current port by start” and “Clear cache on the current port by start“, the folders with cookies and cache will be completely deleted. Thus, the logic of your script should take into account all these nuances.

An example in php using the function of clearing cookies and cache:

php example using app clear functions:

discuss the article on the forum

Leave a Reply

*
*

Required fields are marked *