Hypertext Transfer Protocol (HTTP) has undergone multiple versions of the protocol, many of which are compatible with the previous ones. The RFC 2145 describes the use of HTTP version numbers . The client tells the server at the beginning of the request the version used, and the server uses the same or earlier in your response.
Obsolete. Supports only one command, GE, and it does not specify the Hypertext Transfer Protocol (HTTP) version number. No header supports. Since this version does not support POST, the client can not send a lot of information to the server.
HTTP/1.0 ( May 1996)
This is the first revision of the protocol that specifies the version in communications, and is still widely used, especially in proxy servers.
Early drafts of the document 1995 PEP – an Extension Mechanism for HTTP (the protocol which proposes the extension of Protocol, abbreviated PEP ) made by the World Wide Web Consortium and sent to the Internet Engineering Task Force.
The PEP was originally intended to become a distinctive range. In subsequent drafts, however, the reference to HTTP/1.2 was eliminated. RFC 2774 (experimental), HTTP Extension Framework includes largely PEP. It was published in February 2000.
Example of an HTTP dialog
For a resource with the URL http://www.example.com/index.html
It opens a connection to host http://www.example.com, port 80 is the default port for HTTP.
A message is sent in the following style:
GET / index.html HTTP/1.1
User -Agent: customer-name
The server response comprises headers followed by the requested resource, in the case of a website:
HTTP/1.1 200 OK
Date: Fri, 31 Dec 2003 23:59:59 GMT
Content-Type : text / html
Content-Length : 1221
tuHost <h1> homepage < / h1 >
< / body>
< / html >
Special characters such as punctuation marks, accented characters or umlauts or language writing symbols must be converted to HTML entity for display in a browser.