The VMLogin anti-association browser configuration file settings are very important. If the settings have obvious conflicts or are not in accordance with common sense, then the applied scenarios may be affected. Let’s take a look at some examples of unreasonable configurations: 
WebGL vendor: Like Apple mobile phones and Apple computers.
WebGL vendor ：Apple Inc.
WebGL renderer: Apple GPU
If we are a Windows system, most of them are:
WebGL vendor ：Google Inc.
In the case of our experiment, Chrome browser and Internet Explorer (Edge) test will have two different values for WebGL vendor, Chrome is taken as Google Inc. Internet Explorer (Edge) is taken as Microsoft, so WebGL vendor cannot be fully translated as " Graphics Card Vendor" because it is related to browser developers. We found interestingly that the Firefox browser takes the value of WebGL vendor: Google Inc.
So here we can draw a conclusion: if we identify the User-Agent as Chrome and Firefox browsers, then it is more reasonable to set the WebGL vendor of the windows system to Google Inc..
Master User-Agent configuration has to be familiar with
First of all, let's understand what User-Agent is.
User-Agent will tell the website server what tool the visitor used to request, which contains the relevant version information of the browser and the system.
Every time we HTTP request header will have User-Agent field (as shown below):
User-Agent field explanation
I used the Chrome browser to view the result of User-Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36
User-Agent general format:
Mozilla/5.0 (Platform) Engine Version Browser Version Number
Part 1: Mozilla/5.0
Due to the historical browser wars, at that time, if you wanted to get a web page with rich pictures and texts, you had to declare yourself as a Mozilla browser. This has led to the fact that now User-Agent usually contains the word Mozilla. Out of respect for history, everyone will fill in this section by default.
Part 2: Platform This part can be composed of multiple strings, separated by English half-width semicolons.
Windows NT 10.0 refers to the version of the operating system I use. For example, the win10 I use corresponds to Windows NT 10.0. If I use win7, it corresponds to It is Windows NT 6.1.
Win64; x64 means my operating system is 64-bit
Under Windows system:
Windows NT 5.0 // such as Windows 2000
Windows NT 5.1 // such as Windows XP
Windows NT 6.0 // such as Windows Vista
Windows NT 6.1 // such as Windows 7
Windows NT 6.2 // such as Windows 8
Windows NT 6.3 // such as Windows 8.1
Windows NT 10.0 // Such as Windows 10
Win64; x64 // Win64 on x64
WOW64 // Win32 on x64
Linux system:
X11; Linux i686; // Linux desktop, i686 version
X11; Linux x86_64; // Linux desktop, x86_64 version
X11; Linux i686 on x86_64 // Linux desktop, running on x86_64 i686 version
macOS system:
Macintosh; Intel Mac OS X 10_9_0 // Intel x86 or x86_64
Macintosh; PPC Mac OS X 10_9_0 // PowerPC
Macintosh; Intel Mac OS X 10.12; // Don’t use underscores, use dots.
Part 3: Engine version
AppleWebKit/537.36 (KHTML, like Gecko)...Safari/537.36. Historically, Apple relied on the WebKit core to develop the Safari browser. WebKit includes the WebCore engine, and WebCore is derived from KHTML. Due to historical reasons, the KHTML engine needs to declare that it is "Gecko-like", so the engine part is written like this. Later, Google also used the WebKit core to develop Chrome, so it followed suit. To borrow a quote from Littern: "Chrome wants to get a web page written for Safari, so it decides to pretend to be Safari. Safari uses the WebKit rendering engine, and WebKit pretends to be KHTML, and KHTML pretends to be Gecko. At the same time all Of browsers all claim to be Mozilla.". However, a version of Chrome 28 later switched to the blink kernel, but still retained these strings. Moreover, in the recent dozens of versions, this part has been fixed and has not changed.
Part 4: Browser version
I use the Chrome browser, of which 75.0 is the major version, 3371 is an increasing number, and 100 is the minor version that fixes the vulnerabilities.
Summary of User-Agent: When we set the User-Agent field, we must understand the meaning of all the information in this field, know what we set, and tell the web server what browser we are using and what operation it is System, and some other information. Our other configuration is best not to go against the meaning in User-Agent.
About WebRtc configuration
If you use the replacement mode, if you want the public network IP to be more real, you can select the "Automatically detect IP" option. After selecting it, it will automatically use the configured proxy server information (if a proxy server is set) when you start the browser configuration. Get your exit IP address.
About time zone configuration The
time zone is related to the time zone information of the machine. The VMLogin browser has a local time zone simulation function, and the other is your export IP address. If you want the time zone detection to be the same, you can select "Enable setting time zone based on IP"
After setting the time zone based on IP is selected, the export IP will be automatically detected every time the browser configuration is started, and the time zone of the country where the IP is located will be automatically set.