HTTP - Revision history

DavidB4-bot: /* Request Headers */Spelling/Grammar Check, typos fixed: Referer → Referrer

2016-07-19T16:26:44Z

Request Headers: Spelling/Grammar Check, typos fixed: Referer → Referrer

DavidB4-bot: clean up & uniformity

2016-07-13T13:45:04Z

clean up & uniformity

CPalmer: cat

2011-08-08T14:45:16Z

cat

Ed Poor: expand abbrev.

2010-09-08T12:40:49Z

expand abbrev.

JlHawkwell: wikified "web browser"

2010-08-02T22:57:34Z

wikified "web browser"

JlHawkwell: added the status codes

2010-08-02T22:16:21Z

added the status codes

JlHawkwell: /* History */ another reference fix

2010-08-02T21:00:38Z

History: another reference fix

JlHawkwell: /* History */ fixed references

2010-08-02T20:59:00Z

History: fixed references

JlHawkwell: Added References listing.

2010-08-02T20:56:04Z

Added References listing.

JlHawkwell: /* History */ Added history. I suck at history, so feel free to update or add more.

2010-08-02T20:55:20Z

History: Added history. I suck at history, so feel free to update or add more.

@@ Line 9: / Line 9: @@
 * 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.
-* 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).

@@ Line 1: / Line 1: @@
-'''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 ==
@@ Line 50: / Line 50: @@
 == 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 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 ===
@@ Line 104: / Line 104: @@
 == 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 ==
 {{reflist}}
 [[Category:Internet]]

← Older revision		Revision as of 14:45, August 8, 2011
Line 108:		Line 108:
	== References ==		== References ==
	{{reflist}}		{{reflist}}
		+	[[Category:Internet]]

← Older revision		Revision as of 12:40, September 8, 2010
Line 1:		Line 1:
−	HTTP 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\|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 ==

← Older revision		Revision as of 22:57, August 2, 2010
Line 1:		Line 1:
−	HTTP 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.	+	HTTP 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.

	== Requests ==		== Requests ==

← Older revision		Revision as of 20:56, August 2, 2010
Line 51:		Line 51:
	== History ==		== History ==
	HTTP was developed by Tim Berners-Lee in 1990 [http://www.computerhistory.org/timeline/?year=1990]. 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 [http://tools.ietf.org/html/rfc1945\|RFC-1945] 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 [http://tools.ietf.org/html/rfc2616\|RFC-2616].		HTTP was developed by Tim Berners-Lee in 1990 [http://www.computerhistory.org/timeline/?year=1990]. 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 [http://tools.ietf.org/html/rfc1945\|RFC-1945] 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 [http://tools.ietf.org/html/rfc2616\|RFC-2616].
		+
		+	== References ==
		+	{{reflist}}

← Older revision		Revision as of 20:55, August 2, 2010
Line 50:		Line 50:

	== History ==		== History ==
−	[to ~~be filled~~ in~~, I need a break~~]	+	HTTP was developed by Tim Berners-Lee in 1990 [http://www.computerhistory.org/timeline/?year=1990]. 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 [http://tools.ietf.org/html/rfc1945\|RFC-1945] 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 [http://tools.ietf.org/html/rfc2616\|RFC-2616].