Overview of HTTP

URLs and resources

URLs specify the location of a resource. A resource is often a static file, such as an HTML document, an image, or a sound file. But increasingly, it may be a dynamically generated object, perhaps based on information stored in a database.

When a user agent requests a resource, what is returned is not the resource itself, but some representation of that resource. For example, if the resource is a static file, then what is sent to the user agent is a copy of the file.

Multiple URLs may point to the same resource, and an HTTP server will return appropriate representations of the resource for each URL. For example, an company might make product information available both internally and externally using different URLs for the same product. The internal representation of the product might include information such as internal contact officers for the product, while the external representation might include the location of stores selling the product.

This view of resources means that the HTTP protocol can be fairly simple and straightforward, while an HTTP server can be arbitrarily complex. HTTP has to deliver requests from user agents to servers and return a byte stream, while a server might have to do any amount of processing of the request.

HTTP characteristics

HTTP is a stateless, connectionless, reliable protocol. In the simplest form, each request from a user agent is handled reliably and then the connection is broken. Each request involves a separate TCP connection, so if many resources are required (such as images embedded in an HTML page) then many TCP connections have to be set up and torn down in a short space of time.

Thera are many optimisations in HTTP which add complexity to the simple structure, in order to create a more efficient and reliable protocol.

Versions

There are 3 versions of HTTP

  • Version 0.9 - totally obsolete
  • Version 1.0 - almost obsolete
  • Version 1.1 - current

Each version must understand requests and responses of earlier versions.

HTTP 0.9

Request format

  1. Request = Simple-Request
  3. Simple-Request = "GET" SP Request-URI CRLF

Response format

A response is of the form

  1. Response = Simple-Response
  3. Simple-Response = [Entity-Body]

HTTP 1.0

This version added much more information to the requests and responses. Rather than “grow” the 0.9 format, it was just left alongside the new version.

Request format

The format of requests from client to server is

  1. Request = Simple-Request | Full-Request
  3. Simple-Request = "GET" SP Request-URI CRLF
  5. Full-Request = Request-Line
  6.         *(General-Header
  7.         | Request-Header
  8.         | Entity-Header)
  9.         CRLF
  10.         [Entity-Body]

A Simple-Request is an HTTP/0.9 request and must be replied to by a Simple-Response.

A Request-Line has format

  1. Request-Line = Method SP Request-URI SP HTTP-Version CRLF

where

  1. Method = "GET" | "HEAD" | POST |
  2.      extension-method

e.g. GET http://jan.newmarch.name/index.html HTTP/1.0

Response format

A response is of the form

  1. Response = Simple-Response | Full-Response
  3. Simple-Response = [Entity-Body]
  5. Full-Response = Status-Line
  6.         *(General-Header 
  7.         | Response-Header
  8.         | Entity-Header)
  9.         CRLF
  10.         [Entity-Body]

The Status-Line gives information about the fate of the request:

  1. Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF

e.g.

  1. HTTP/1.0 200 OK
  3. The codes are
  5. Status-Code =      "200" ; OK
  6.         | "201" ; Created
  7.         | "202" ; Accepted
  8.         | "204" ; No Content
  9.         | "301" ; Moved permanently
  10.         | "302" ; Moved temporarily
  11.         | "304" ; Not modified
  12.         | "400" ; Bad request
  13.         | "401" ; Unauthorised
  14.         | "403" ; Forbidden
  15.         | "404" ; Not found
  16.         | "500" ; Internal server error
  17.         | "501" ; Not implemented
  18.         | "502" ; Bad gateway
  19.         | "503" | Service unavailable
  20.         | extension-code

The Entity-Header contains useful information about the Entity-Body to follow

  1. Entity-Header =    Allow
  2.         | Content-Encoding
  3.         | Content-Length
  4.         | Content-Type
  5.         | Expires
  6.         | Last-Modified
  7.         | extension-header

For example

  1. HTTP/1.1 200 OK
  2. Date: Fri, 29 Aug 2003 00:59:56 GMT
  3. Server: Apache/2.0.40 (Unix)
  4. Accept-Ranges: bytes
  5. Content-Length: 1595
  6. Connection: close
  7. Content-Type: text/html; charset=ISO-8859-1

HTTP 1.1

HTTP 1.1 fixes many problems with HTTP 1.0, but is more complex because of it. This version is done by extending or refining the options available to HTTP 1.0. e.g.

  • there are more commands such as TRACE and CONNECT
  • you should use absolute URLs, particularly for connecting by proxies e.g
  1. GET http://www.w3.org/index.html HTTP/1.1
  • there are more attributes such as If-Modified-Since, also for use by proxies

The changes include

  • hostname identification (allows virtual hosts)
  • content negotiation (multiple languages)
  • persistent connections (reduces TCP overheads - this is very messy)
  • chunked transfers
  • byte ranges (request parts of documents)
  • proxy support

The 0.9 protocol took one page. The 1.0 protocol was described in about 20 pages. 1.1 takes 120 pages.