HTTP/1.1 - 版本历史

Riguz：Riguz moved page Hypertext Transfer Protocol -- HTTP/1.1 to HTTP/1.1 without leaving a redirect

2023-12-06T07:26:08Z

Riguz moved page Hypertext Transfer Protocol -- HTTP/1.1 to HTTP/1.1 without leaving a redirect

←上一版本	2023年12月6日 (三) 07:26的版本
（没有差异）

Riguz：/* OPTIONS */

2023-12-05T14:08:15Z

OPTIONS

@@ 第53行： / 第53行： @@
 OPTIONS /index.html HTTP/1.1
 OPTIONS * HTTP/1.1
 </syntaxhighlight>

Riguz：/* CONNECT */

2023-12-05T14:04:32Z

CONNECT

←上一版本		2023年12月5日 (二) 14:04的版本
第43行：		第43行：
	a web client uses CONNECT only when it knows it talks to a proxy and the final URI begins with https://.		a web client uses CONNECT only when it knows it talks to a proxy and the final URI begins with https://.

			<syntaxhighlight lang="HTTP">
			CONNECT www.example.com:443 HTTP/1.1
			</syntaxhighlight>

			=== OPTIONS ===
			The HTTP OPTIONS method requests permitted communication options for a given URL or server. A client can specify a URL with this method, or an asterisk (*) to refer to the entire server

	<syntaxhighlight lang="HTTP">		<syntaxhighlight lang="HTTP">
	~~CONNECT www~~.~~example~~.~~com:443~~ HTTP/1.1		OPTIONS /index.html HTTP/1.1
			OPTIONS * HTTP/1.1
	</syntaxhighlight>		</syntaxhighlight>

Riguz：/* Persistent connections */

2023-12-05T11:02:09Z

Persistent connections

←上一版本		2023年12月5日 (二) 11:02的版本
第27行：		第27行：

	In HTTP 1.1, it is possible to execute several requests using a single connection. HTTP persistent connection, also called HTTP keep-alive, or HTTP connection reuse, is the idea of using a single TCP connection to send and receive multiple HTTP requests/responses, as opposed to opening a new connection for every single request/response pair. The newer HTTP/2 protocol uses the same idea and takes it further to allow multiple concurrent requests/responses to be multiplexed over a single connection.		In HTTP 1.1, it is possible to execute several requests using a single connection. HTTP persistent connection, also called HTTP keep-alive, or HTTP connection reuse, is the idea of using a single TCP connection to send and receive multiple HTTP requests/responses, as opposed to opening a new connection for every single request/response pair. The newer HTTP/2 protocol uses the same idea and takes it further to allow multiple concurrent requests/responses to be multiplexed over a single connection.

			In HTTP 1.1, all connections are considered persistent unless declared otherwise.

	== New methods ==		== New methods ==

Riguz：/* Persistent connections */

2023-12-05T10:58:57Z

Persistent connections

←上一版本		2023年12月5日 (二) 10:58的版本
第26行：		第26行：
	In HTTP 1.0 you had to open a new connection for each request/response pair. And after each response the connection would be closed. This lead to some big efficiency problems because of [[TCP Slow Start]].		In HTTP 1.0 you had to open a new connection for each request/response pair. And after each response the connection would be closed. This lead to some big efficiency problems because of [[TCP Slow Start]].

	In HTTP 1.1, it is possible to execute several requests using a single connection.		In HTTP 1.1, it is possible to execute several requests using a single connection. HTTP persistent connection, also called HTTP keep-alive, or HTTP connection reuse, is the idea of using a single TCP connection to send and receive multiple HTTP requests/responses, as opposed to opening a new connection for every single request/response pair. The newer HTTP/2 protocol uses the same idea and takes it further to allow multiple concurrent requests/responses to be multiplexed over a single connection.

	== New methods ==		== New methods ==

Riguz：/* CONNECT */

2023-12-05T10:51:43Z

CONNECT

←上一版本		2023年12月5日 (二) 10:51的版本
第38行：		第38行：

	For example, the CONNECT method can be used to access websites that use TLS (HTTPS). The client asks an HTTP Proxy server to tunnel the TCP connection to the desired destination. The server then proceeds to make the connection on behalf of the client. Once the connection has been established by the server, the Proxy server continues to proxy the TCP stream to and from the client<ref>https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT</ref>.		For example, the CONNECT method can be used to access websites that use TLS (HTTPS). The client asks an HTTP Proxy server to tunnel the TCP connection to the desired destination. The server then proceeds to make the connection on behalf of the client. Once the connection has been established by the server, the Proxy server continues to proxy the TCP stream to and from the client<ref>https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT</ref>.

			a web client uses CONNECT only when it knows it talks to a proxy and the final URI begins with https://.

Riguz：/* New methods */

2023-12-05T10:48:44Z

New methods

←上一版本		2023年12月5日 (二) 10:48的版本
第32行：		第32行：

	HTTP/1.1 introduces the <syntaxhighlight lang="bash" inline>OPTIONS</syntaxhighlight> method. An HTTP client can use this method to determine the abilities of the HTTP server. It's mostly used for Cross Origin Resource Sharing in web applications.		HTTP/1.1 introduces the <syntaxhighlight lang="bash" inline>OPTIONS</syntaxhighlight> method. An HTTP client can use this method to determine the abilities of the HTTP server. It's mostly used for Cross Origin Resource Sharing in web applications.

			=== CONNECT ===

			The HTTP CONNECT method starts two-way communications with the requested resource. It can be used to open a tunnel.

			For example, the CONNECT method can be used to access websites that use TLS (HTTPS). The client asks an HTTP Proxy server to tunnel the TCP connection to the desired destination. The server then proceeds to make the connection on behalf of the client. Once the connection has been established by the server, the Proxy server continues to proxy the TCP stream to and from the client<ref>https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT</ref>.


			<syntaxhighlight lang="HTTP">
			CONNECT www.example.com:443 HTTP/1.1
			</syntaxhighlight>

	== 100 Continue status ==		== 100 Continue status ==

Riguz：/* New methods */

2023-12-05T10:40:36Z

New methods

←上一版本		2023年12月5日 (二) 10:40的版本
第31行：		第31行：
	besides the already available methods of HTTP 1.0, the 1.1 version added six extra methods: PUT, PATCH, DELETE, CONNECT, TRACE, and OPTIONS.		besides the already available methods of HTTP 1.0, the 1.1 version added six extra methods: PUT, PATCH, DELETE, CONNECT, TRACE, and OPTIONS.

	HTTP/1.1 introduces the OPTIONS method. An HTTP client can use this method to determine the abilities of the HTTP server. It's mostly used for Cross Origin Resource Sharing in web applications.		HTTP/1.1 introduces the <syntaxhighlight lang="bash" inline>OPTIONS</syntaxhighlight> method. An HTTP client can use this method to determine the abilities of the HTTP server. It's mostly used for Cross Origin Resource Sharing in web applications.

	== 100 Continue status ==		== 100 Continue status ==

Riguz：/* Host header */

2023-12-05T10:39:32Z

Host header

←上一版本		2023年12月5日 (二) 10:39的版本
第16行：		第16行：
	HTTP 1.0 does not officially require the host header. HTTP 1.1 requires it by the specification. The host header is specially important to route messages through proxy servers, allowing to distinguish domains that point to the same IP		HTTP 1.0 does not officially require the host header. HTTP 1.1 requires it by the specification. The host header is specially important to route messages through proxy servers, allowing to distinguish domains that point to the same IP

	<~~pre~~>		<syntaxhighlight lang="HTTP" inline>GET /hello.txt HTTP/1.1
	GET /hello.txt HTTP/1.1
	Host: www.example.com		Host: www.example.com
	</~~pre~~>		</syntaxhighlight>

	This header is useful because it allows you to route a message through proxy servers, and also because your web server can distinguish between different sites on the same server.		This header is useful because it allows you to route a message through proxy servers, and also because your web server can distinguish between different sites on the same server.

Riguz：/* HTTP 1.1 vs HTTP 1.0 */

2023-12-05T10:06:39Z

HTTP 1.1 vs HTTP 1.0

←上一版本		2023年12月5日 (二) 10:06的版本
第11行：		第11行：
	Version 1.1 of HTTP was released in 1997, only one year after the previous version 1.0. HTTP 1.1 is an enhancement of HTTP 1.0, providing several extensions.		Version 1.1 of HTTP was released in 1997, only one year after the previous version 1.0. HTTP 1.1 is an enhancement of HTTP 1.0, providing several extensions.

	Among the most relevant enhancements, we can cite the following<ref>~~HTTP~~ 1.0 vs 1.1 ~~- Stack Overflow~~</ref>:		Among the most relevant enhancements, we can cite the following<ref>https://stackoverflow.com/questions/246859/http-1-0-vs-1-1</ref>:

	== Host header ==		== Host header ==

HTTP/1.1 - 版本历史

Riguz：​Riguz moved page Hypertext Transfer Protocol -- HTTP/1.1 to HTTP/1.1 without leaving a redirect

Riguz：​/* OPTIONS */

Riguz：​/* CONNECT */

Riguz：​/* Persistent connections */

Riguz：​/* Persistent connections */

Riguz：​/* CONNECT */

Riguz：​/* New methods */

Riguz：​/* New methods */

Riguz：​/* Host header */

Riguz：​/* HTTP 1.1 vs HTTP 1.0 */

Riguz：Riguz moved page Hypertext Transfer Protocol -- HTTP/1.1 to HTTP/1.1 without leaving a redirect

Riguz：/* OPTIONS */

Riguz：/* CONNECT */

Riguz：/* Persistent connections */

Riguz：/* Persistent connections */

Riguz：/* CONNECT */

Riguz：/* New methods */

Riguz：/* New methods */

Riguz：/* Host header */

Riguz：/* HTTP 1.1 vs HTTP 1.0 */