What is option * HTTP/1.0"

[Isiah]

Is HTTP/1.0 does it compare to its predecessor? The first improvement is for the convenience of navigation: HTTP/1.0 can handle the caches (The mechanism remains fairly primitive). Then we can send information to the server (thanks to a new method: the POST). HTTP/1.0 know then recognize when a query failed (The famous "404 not Found"). Finally, HTTP/1.0 allows users to authenticate, for example, for access to a hidden part of a site. Have you any idea about option in * HTTP/1.0". Please help.

[MindSpace]

An HTTP/1.0 request consists of three things: method (Which to say what we do), followed immediately by Headers (To give more details) an extra line break and finally the possible entity body (Information to send to the server, ie the content of a form or a file). We will see below that Headers are also composed of three parts (the last option, information on data below).

[Zecho]

The requests in HTTP/1.0 can be of 3 kinds (there are 3 different methods): method GETThe method HEAD and method POST.Method GET is the same as in HTTP/0.9: it allows retrieve the document specified by the URI. The role of the method HEAD will be described in the section dealing caches. It quickly allows to retrieve only the header part a complete response.

[opaper]

HTTP/1.0: he does not handle relative URLs when there is a virtual server configuration. Specifically, if we make a HTTP/1.0 request on a machine that hosts in asking for the file / Index.html (Application form: GET / index.html HTTP/1.0), And although the server does not know which page to index.html. In HTTP/1.0, we must specify the absolute URL of documents (GET HTTP/1.0).

[Reegan]

When you make a request to a server must send a prior header for clarify. This header is actually optional: for compatibility reasons with HTTP/0.9 clients, we can complete an application by typing 2 times without input giving header. Otherwise, the header is composed of more than 3 parts, the latter is mandatory only if you send data to the server:
* generic header: The exchange, the application or response,
* header of the request: Details on the application itself,
* header entity: Details on the data sent (Meta information)

[Appaji]

HTTP/1.0 server response is very similar to the client's request for above, The difference being that the server first sends a status and not a method. The rest (headers and body of the entity) generally operate the same way. With HTTP/1.0, the client knows the type of response, through the header of the server response. In fact, the first thing that returns the server, is how the transaction went.

[KennedII]

HTTP/1.0 introduces special instructions such as Date, Expires and Last-Modified , which determine when a requested document changed since the last time, or calculate the time that must remain a resource in the cache, or simply to tell from when you should ask the server the new document (Directive Expires).