Changes

'''HTTP''' (HyperText Transfer Protocol) is a single-transaction text-based data transfer protocol using the request-and-respond method.  Following with the client-server model of peer communications, a ''client'' constitutes software that makes requests, an example of which is a typical [[Web_browser|web browser]].  ''Servers'' accept connections and requests from clients and return the results to the client, often with intermediate processing that determines the content to return, or modifies content to return.  Software such as MediaWiki used by [[Conservapedia]] runs on the server and performs this intermediate processing.  Software on the server may also act as a client in the case of a reverse proxy for load balancing, or to obtain content from other servers, as is commonly done in the fight against internet spam.

'''HTTP''' (HyperText Transfer Protocol) is a single-transaction text-based data transfer protocol using the request-and-respond method.  Following with the client-server model of peer communications, a ''client'' constitutes software that makes requests, an example of which is a typical [[web browser]].  ''Servers'' accept connections and requests from clients and return the results to the client, often with intermediate processing that determines the content to return, or modifies content to return.  Software such as MediaWiki used by [[Conservapedia]] runs on the server and performs this intermediate processing.  Software on the server may also act as a client in the case of a reverse proxy for load balancing, or to obtain content from other servers, as is commonly done in the fight against internet spam.

== Requests ==

== Requests ==

* Accept - List of content types the client is willing to accept.

* Accept - List of content types the client is willing to accept.

* User-Agent - A simple string that identifies the client, usually used by web browsers to provide a scary amount of information that is only sometimes useful.

* User-Agent - A simple string that identifies the client, usually used by web browsers to provide a scary amount of information that is only sometimes useful.

* Referer - If the client software is a web browser, this header contains the complete URL from the previous page.  Only provided if the user clicked a link.

* Referrer - If the client software is a web browser, this header contains the complete URL from the previous page.  Only provided if the user clicked a link.

* Cookie - Cookies are small bits of text that are meant to carry information across requests.  The most common uses of this data include authentication information (when you log into a website) and tracking information (such as a unique client ID used by advertisers for demographics collection).

* Cookie - Cookies are small bits of text that are meant to carry information across requests.  The most common uses of this data include authentication information (when you log into a website) and tracking information (such as a unique client ID used by advertisers for demographics collection).

== Response Status Codes ==

== Response Status Codes ==

Multiple response codes are defined in RFC-1945<ref name="rfc1945">http://tools.ietf.org/html/rfc1945</ref> and RFC-2616<ref name="rfc2616">http://tools.ietf.org/html/rfc2616</ref>. These status codes can tell the client about a variety of conditions including success, failure, or something else entirely.

Multiple response codes are defined in RFC-1945<ref name="rfc1945">http://tools.ietf.org/html/rfc1945</ref> and RFC-2616.<ref name="rfc2616">http://tools.ietf.org/html/rfc2616</ref>  These status codes can tell the client about a variety of conditions including success, failure, or something else entirely.

=== 100 Series ===

=== 100 Series ===

* '''100 Continue''' - For requests with long request bodies, this is used by the server to inform the client that it should continue sending the request body.

* '''100 Continue''' - For requests with long request bodies, this is used by the server to inform the client that it should continue sending the request body.

* '''101 Switching Protocols''' - Used by the server to inform the client that it is switching protocols.  This may be done to change the HTTP version used for the request, or to switch to an extension of HTTP, such as WebDAV<ref name="rfc4918">http://tools.ietf.org/html/rfc4918</ref>.

* '''101 Switching Protocols''' - Used by the server to inform the client that it is switching protocols.  This may be done to change the HTTP version used for the request, or to switch to an extension of HTTP, such as WebDAV.<ref name="rfc4918">http://tools.ietf.org/html/rfc4918</ref>

=== 200 Series ===

=== 200 Series ===

== History ==

== History ==

HTTP was developed by Tim Berners-Lee in 1990 <ref>http://www.computerhistory.org/timeline/?year=1990</ref>. At the time it was known as HTTP/0.9 and was updated and extended many times by many people, yet was not a standard until it was published in RFC-1945<ref name="rfc1945" /> as HTTP/1.0.  HTTP was designed to supplement and transfer HTML, also developed by Tim Berners-Lee.  Modern servers and clients typically use HTTP/1.1 which was defined as an update to HTTP/1.0 in RFC-2616<ref name="rfc2616" />.

HTTP was developed by Tim Berners-Lee in 1990.<ref>http://www.computerhistory.org/timeline/?year=1990</ref>  At the time it was known as HTTP/0.9 and was updated and extended many times by many people, yet was not a standard until it was published in RFC-1945<ref name="rfc1945" /> as HTTP/1.0.  HTTP was designed to supplement and transfer HTML, also developed by Tim Berners-Lee.  Modern servers and clients typically use HTTP/1.1 which was defined as an update to HTTP/1.0 in RFC-2616.<ref name="rfc2616" />

== References ==

== References ==

{{reflist}}

{{reflist}}

[[Category:Internet]]

[[Category:Internet]]