Scenario :
When sending http requests, chrome and QQ browsers press F12 to debug, click on the request in Network, as shown below
After sending the request, due to various reasons, such as network delay, server-side logic errors, the most likely server-side operation consumes too much time, resulting in the client-side not receiving a response for a long time.
The server does not give the impact of the response:
Subsequent requests to this url will not be sent, and the browser will intercept it. After the interface times out, no response will be given, resulting in subsequent requests being ignored by the browser.
Solution : After searching, it was found to be an interface performance problem. The previous writing method had a performance problem that took too long for the query after the data surge, which was caused by the server returning a timeout.