http/1.1 Learning

found that the HTTP protocol can not blurt out, so anger over the data, RFC2616.

In its abstract it is said that HTTP, Application layer protocol, generic, stateless. One of its features is the typing and negotiation of data representation, allowing systems to be built independently of the data being TRA Nsferred.

Messages is transmitted in a format similar to that used by Internet mail, and is defined by MIME (Multipurpose Internet Mail Extensions).

Terms

Connection: A transport-layer virtual loop created between two programs for communication purposes.

The basic unit of Message:http communication consists of a structured eight-bit group (octets) sequence that conforms to the syntax and is transmitted through connection.

Request: An HTTP request message.

Response: An HTTP response message.

Resource: A network data object or service that can be determined by a URI. Resources may be presented in multiple representations (e.g. multiple languages, multiple formats, multiple sizes, etc.).

Entity:request or response to host the transmitted information. An entity consists of metadata (Entity-header fields form) and content (Entity-body).

The entity in Representation:response is subject to the content negotiation. A special response status may exist multiple representations.

Content negotiation: When serving a request, select the appropriate representation mechanism. The representation of any response entity can be negotiated (including error responses).

Variant: At any moment, a resource may be associated to one or more representation (s). Each of the representation is a variant. The use of Variant terminology does not imply that resource is subject to content negotiation.

Client: A program whose purpose for creating connections is to send requests.

User agent: The client that initiated the request. Typically a browser, editor, spiders, or other end-user tool.

Server: A application program, accepting connections to serve requests, will send back responses. Any program can be both client and server.

Origin server: A server with the specified resource, or the resource that will be created.

Proxy: Intermediate program that acts as both the server and client roles to initiate requests on behalf of other clients. A "Transparent proxy" is said that in addition to the necessary proxy authentication and identification, will not modify the request or response proxy. A "Non-transparent proxy" modifies the request or response to provide some additional services to the user agent, such as group annotation services, media type Transformation, protocol reduction, or anonymity filtering.

Gateway: one server, but for some servers plays the intermediate level. Unlike proxy, a gateway receives requests as if it were requested resource's original server; The client initiating the request does not realize that it is communicating with the same gateway.

Tunnel:

http/1.1 Learning