From the perspective of development: http request 408 error and solution [Request timeout]

Introduction

In your web server's opinion, in 1) Establish an IP connection (Nested-socket) between the client (such as your browser or our checkupdown robot) and the server, and 2) the server disconnects the connection because the interval between the received data is too long. The socket connection has actually expired-your web server has sent a 'timeout' signal to the specified socket connection. Client requests must be repeated in a timely manner.

Error 408 in HTTP Loop

Any client (such as your browser or our checkupdown robot) must use the following loop:

• Obtain an IP address from the IP address of your site (that is, the URL of your site, without the starting 'HTTP. This ing relationship is provided by the Domain Name Server (DNSS.
• Open an IP socket to connect to the IP address.
• Write the HTTP data stream through this socket.
• Accept the response HTTP data streams from your web server. This data stream includes status encoding, and its value depends on the HTTP protocol. Parse the data stream to get status code and other useful information.

This error is generated in the last step described above, that is, when the client receives the HTTP status code and recognizes it as '123'

Solution to 408 error-General Method

408 errors are often hard to solve. They usually involve one-time changes in system workload or system operations.

If you continuously see error 408, you must first consider the workload of the web server, especially during the time period when error 408 is generated. If the workload is low, you also need to consider the workload of the client system. If the computer systems at both ends of the socket connection seem to be operating normally, the temporary increase in Internet traffic may be the root cause.

Solve the 408 error-checkupdown

This error cannot occur in your checkupdown account, because it usually takes only a short interval (in milliseconds) between 1) socket activation and 2) Writing HTTP data streams through this socket ). In special circumstances, this interval may increase due to some operations on our computer system. For example, we suspend an execution program, which occurs after the socket is generated. Or these two steps happen quickly in our system, but the second step encounters unreasonable latency on the Internet.
Your web server may also set the acceptable interval between the two steps to a very low level. If your server is busy, it may feel a little impatient to try a link that is a little slow.

In any of these cases, error 408 may be generated. But they are not easy to happen. In normal IP communication, the time interval between the two steps should be much less than 10 seconds, which should be completely acceptable to your web server.