HTTP 400
Closed
Oki
-
Aug 19, 2009 at 01:41 PM
xpcman Posts 19528 Registration date Wednesday October 8, 2008 Status Contributor Last seen June 15, 2019 - Aug 19, 2009 at 02:26 PM
xpcman Posts 19528 Registration date Wednesday October 8, 2008 Status Contributor Last seen June 15, 2019 - Aug 19, 2009 at 02:26 PM
1 response
xpcman
Posts
19528
Registration date
Wednesday October 8, 2008
Status
Contributor
Last seen
June 15, 2019
1,824
Aug 19, 2009 at 02:26 PM
Aug 19, 2009 at 02:26 PM
Introduction
The Web server (running the Web site) thinks that the data stream sent by the client (e.g. your Web browser ) was 'malformed' i.e. did not respect the HTTP protocol completely. So the Web server was unable to understand the request and process it.
It almost always means bad programming of the client system and/or the Web server.
400 errors in the HTTP cycle
Any client (e.g. your Web browser) goes through the following cycle:
* 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.
This error occurs in the final step above when the client receives an HTTP status code it recognizes as '400'.
The Web server (running the Web site) thinks that the data stream sent by the client (e.g. your Web browser ) was 'malformed' i.e. did not respect the HTTP protocol completely. So the Web server was unable to understand the request and process it.
It almost always means bad programming of the client system and/or the Web server.
400 errors in the HTTP cycle
Any client (e.g. your Web browser) goes through the following cycle:
* 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.
This error occurs in the final step above when the client receives an HTTP status code it recognizes as '400'.
