GuidesHTTP Explained Page 5

HTTP Explained Page 5

Here is an example of an HTTP response from a server to a client request:

 HTTP/1.0 200 OK Date: Wednesday, 02-Feb-95 23:04:12 
GMT Server: NCSA/1.3 MIME-version: 1.0
Last-modified: Monday, 15-Nov-93 23:33:16 GMT Content-type: text/html
Content-length: 2345 * a blank line * . . .
  • The server agrees to use HTTP version 1.0 for communication and sends the status 200 indicating it has successfully processed the client’s request.

  • It then sends the date and identifies itself as an NCSA HTTP server.

  • It also indicates it is using MIME version 1.0 to describe the information it is sending, and includes the MIME-type of the information about to be sent in the “Content-type:” header.

  • Finally, it sends the number of characters it is going to send, followed by a blank line and the data itself.

  • Client and server headers are RFC 822 compliant mail headers. A Client may send any number of Accept: headers and the server is expected to convert the data into a form the client can accept.

Latest Posts

Related Stories