Hypertxt Transfer Protocol (HTTP)

Hypertext Transfer Protocol (HTTP) is an application layer network protocols used for distributed information systems, collaborative, and using hypermedia. Its use in making a lot of resources that are connected by links, called hypertext documents, which later formed the World Wide Web in 1990 by British physicist, Tim Berners-Lee. Up to now, there are two major versions of the HTTP protocol, ie HTTP/1.0 which uses a separate connection for each document, and HTTP/1.1 that can use the same connection to perform the transaction. Thus, HTTP/1.1 can be much faster because it does not have to waste time making repeated connections.

HTTP standards development has been carried out by the World Wide Web Consortium (World Wide Web Consortium/W3C) and Internet Engineering Task Force (IETF), which led to the publication of several documents Request for Comments (RFC), and is the most widely referenced RFC 2616 ( published in June 1999), which defines HTTP/1.1.

Support for HTTP/1.1 is not passed, at which time the RFC 2068, it was quickly adopted by many Web developers explorers beginning in 1996. As of March 1996, which has not been ratified HTTP/1.1 was supported by Netscape 2.0, Netscape Navigator Gold 2:01, Mosaic 2.7, Lynx 2.5, and in Microsoft Internet Explorer 3.0. Adoption by end users was also fast Web browser. In March 2006, one web hosting company reported that over 40% of Web browser used on the Internet is a web browser that supports HTTP/1.1. [1] The same company also reported that as of June 1996, 65% of all the explorers who access their servers is a Web browser that supports HTTP/1.1. HTTP/1.1 standard as defined in RFC 2068 was officially released in January 1997. Improvement and renewal of the HTTP/1.1 standard RFC 2616 document released by June 1999.

HTTP protocol is a request / reply between the client and the server. An HTTP client (like a web browser or robots, etc.), usually start with a request to make connections to a specific port on a specific Webhosting server (usually port 80). Client sends an HTTP request is also known by the user agent. The server to respond, which saves resources such as HTML files and images, also known as the origin server. In between the user agent and the origin server, there may be a link, as a proxy, gateway, and tunnel.

HTTP is not limited to use with TCP / IP, although HTTP is one application protocol TCP / IP the most popular over the Internet. Indeed HTTP can be implemented on top of the other protocols in the Internet or over other networks. as mentioned in the "implemented a on top of any other protocol on the Internet, or on other networks.", but the HTTP protocol requires a reliable transport layer. Other protocols that provide services and security as it can also be used.

Request Metode For HTTP

Nine sets HTTP method (sometimes referred to as "verbs") indicating the action you want performed on unidentified sources. It is represented by this source, in the form of existing data or data that is created dynamically, depending on the implementation of the waiter. This source is usually associated with the file or the output from executing files residing on server.

HEAD
     Asking for responses that are identical to the corresponding responses to the GET request, but without the response body. This is useful for accessing meta information is written in response to the head without the need to transport the entire content.
GET
     Requested certain representations sources. Requests using GET (and a few other HTTP methods) "should not have the benefit of taking action in addition to accessing". W3C has published a guide to the principles of this difference by saying, "Web application design should comply with the principles above, and similar restrictions".
POST
     Transmit the data to be processed (eg, from an HTML form) to the identified resource. The data included in the request body. This can result in the formation of a new source or update an existing source or both.
PUT
     Uploading a particular source of representations.
DELETE
     Remove a specific source.
TRACE
     Echo back the received request, so that the client can see the changes or additions made by the waiter intermediaries.
OPTIONS
     Returns the HTTP methods supported waiter for a particular URL. This can be used to check the functionality of the web waiter asks  rather than a specific source functionality.
CONNECT
     Exchange tunnel connection requests with TCP / IP transparent, usually to facilitate SSL-encrypted communication (HTTPS) through an HTTP proxy is not encrypted.
PATCH
     Apply partial modifications to the source.

HTTP waiter asked to implement at least the GET and HEAD methods and, if possible, the methods OPTIONS.