HTTP Error 408
Request timeout
Introduction
The Web server (running the Web site) thinks that there has been too long an interval of time between 1) the establishment of an IP connection (socket) between the client (e.g. your Web browser or our CheckUpDown robot) and the server and 2) the receipt of any data on that socket, so the server has dropped the connection. The socket connection has actually been lost - the Web server has 'timed out' on that particular socket connection. The request from the client must be repeated - in a timely manner.408 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:Fixing 408 errors - general
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '408'. (Last updated: March 2012).
- Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
- Open an IP socket connection to that IP address.
- Write an HTTP data stream through that socket.
- Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
408 errors are often difficult to resolve. They typically involve one-off variations in system workload or operations.Fixing 408 errors - CheckUpDown
If you see persistent 408 errors, the first thing to consider is the workload on the Web server - particularly around the time the 408 errors were generated. If this is light, then you also need to consider workload on the client system. If the computer systems on both ends of the socket connection seem to be running normally, then temporary Internet surges may be to blame.
Below are the full error messages that may be seen when the computer is booting.
NTLDR is Missing
Press any key to restart
Boot: Couldn't find NTLDR
Please insert another disk
NTLDR is missing
Press Ctrl Alt Del to Restart
Causes
Computer is booting from a non-bootable source
Many times this error is caused when the computer is attempting to boot from a non-bootable floppy disk or CD-ROM. First verify that no floppy diskette or CD is in the computer, unless you are attempting to boot from a diskette.
Note: This error has also been known to occur when a memory stick is in a card reader and the computer is attempting to boot from it. If you have any card reader or flash reader make sure that no memory stick is inside the computer. Additionally disconnect all USB drives, cameras, ipods, iphones, etc. from the computer.
If you are attempting to boot from a floppy diskette and are receiving this error message it is likely that the diskette does not have all the necessary files or is corrupt.
If you are attempting to install Windows XP or Windows 2000 and are receiving this error message as the computer is booting verify that your computer BIOS has the proper boot settings. For example, if you are attempting to run the install from the CD-ROM make sure the CD-ROM is the first boot device, and not the hard disk drive.
Second, when the computer is booting you should receive the below prompt.
Press any key to boot from the CD
Important: When you see this message press any key such as the Enter key immediately, otherwise it will try booting from the hard drive and likely get the NTLDR error again.
Note: If you are not receiving the above message and your BIOS boot options are set properly it's also possible that your CD-ROM drive may not be booting from the CD-ROM properly. Verify the jumpers are set properly on the CD-ROM drive.
31 views
Usually answered in minutes!
It has to do with connection I believe! Unplug everything and let it reboot! should fix the problem!
×