Error 7 (net: ERR_TIMED_OUT) caused by Chrome "False Start": The ope

English prompt: This webpage is not available. Error 7 (net: ERR_TIMED_OUT): The operation timed out.
Note: This webpage cannot be accessed. Error 7 (net: ERR_TIMED_OUT): Operation timeout.
(This screen has a license with Windows blue screen)
In the above picture, have you ever met me when you used Chrome to visit the garden? Have you ever been depressed ?...
I have met many times, and I am deeply depressed. I even want to break up with Chrome. You know this kind of love and hate...
There may be love for no reason, but there is no hate for no reason. Sometimes hate is because of love, sometimes hate is because of misunderstanding. Do not give up because of hate, but find the reason.

In the Code world, there is a reason for all problems, and the code won't roll the dice.
In The face of problems, there is no other choice, only to turn depressing into strength, find The real reason for "Error 7 (net: ERR_TIMED_OUT): The operation timed out.
In the vast ocean of the Internet, Google took the ship and found two important clues:
1. Google Chrome's new False Start "Feature"
1.1 according to my understanding, I may translate:
Chrome introduced a new feature, "False Start", to improve the speed of secure communication based on SSL and TLS (used by HTTPS ). Establishing a secure channel between the browser and the Web server requires a round-trip message (one time), while "False Start" reduces one of them, from "round-trip" to "One-Way" (whether there is no return or no return, I do not know yet ).
"False Start" improves the access speed of websites using HTTPS protocol. However, the "False Start ", chrome can intelligently determine whether the accessed website supports "False Start" (I guess this judgment is "cloud judgment" and need to connect to Google's server). If this judgment is not supported, chrome automatically disables "False Start ".
Therefore, when a user who uses a private LAN (cannot access the Internet, and the "cloud judgment" he guessed previously cannot work) accesses a site that does not support "False Start" (the old version of Apache, IIS, Tomcat, IIS not mentioned here), "Error 7 (net: ERR_TIMED_OUT): The operation timed out" will appear ".
1.2 my analysis:
A) The Web server does not support "False Start"; B) Chrome cannot determine whether the target site supports "False Start". By default, "False Start" is enabled ".
Therefore, when Chrome accesses a site that does not support "False Start" in the form of "False Start", "Error 7 (net: ERR_TIMED_OUT) will appear ): the operation timed out ".
According to our actual situation, "Error 7 (net: ERR_TIMED_OUT): The operation timed out" does not appear every time you visit The garden. It appears irregular and will not appear in most cases, it will be normal if you click it multiple times after it appears. I guess that when Chrome correctly determines that garden does not support "False Start", this problem will not occur (because our Web server uses IIS, it can be inferred that IIS does not support "False Start "). For some reason, Chrome cannot determine whether the target site supports "False Start". By default, "False Start" is enabled for access. According to previous speculation, Chrome's judgment may be "cloud judgment". The reason why it is impossible to judge is that it cannot be connected to the Google server for a short time.
2. Request to look into IIS7 support for "SSL False Start"
This is a post posted on Microsoft's IIS official site. The author found that IIS7/7.5 does not support Chrome "False Start" and reported it to the Forum.
The answer is: "False Start" is not an SSL standard. It is added by Chrome to improve SSL performance. other browsers do not support this function.
My feelings: Let Microsoft specifically improve IIS for Chrome. After the improvement, Chrome performs better in SSL than IE, So Microsoft will not do anything.

Problem cause Summary
1. IIS does not support Chrome's "False Start" feature.
2. For some reason, Chrome cannot be connected to the Google server for a short time, so it cannot determine whether the target site supports "False Start". Therefore, "False Start" is enabled by default for access. (Personal guess, unconfirmed)
 

Solution
Disable Chrome's "False Start" feature. Operation Method:
1. Create a Chrome shortcut on the desktop;
2. Select the shortcut and right-click "properties )";
3. In the define target (targetmediaworkflow), enter the parameter "-disable-ssl-false-start" after chome.exe.


 

This method is indeed valid and has been verified.
Google Chrome's new False Start "Feature" also mentions another method, using the parameter-use-system-ssl, force Chrome to use the Windows-SCHANNEL ).
However, for a website, it is obviously unrealistic for all users using Chrome to make such changes. A better solution is as follows:
1. Wait for Chrome improvement. "False Start" is disabled by default ";
2. Wait for "False Start" to become the SSL standard, so IIS has to support it;
3. added a reverse proxy server that supports "False Start" before IIS.




Summary
There is a story between Chrome and IIS, but we don't know who to blame because of the troubles of many people. But we can get inspiration from it-how important standards are in the software industry!


Author dudu