HTTP/3 - 版本历史

Riguz：/* Browser support */

2024-01-31T05:44:35Z

Browser support

←上一版本		2024年1月31日 (三) 05:44的版本
第160行：		第160行：
	/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --enable-quic --origin-to-force-quic-on=localhost:443		/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --enable-quic --origin-to-force-quic-on=localhost:443
	</syntaxhighlight>		</syntaxhighlight>

			If the scheme is not h3 for a h3-supported site, check it with curl first, might be a firewall problem.

			[[Image:h3-curl.png\|600px]]

	= FAQ =		= FAQ =

Riguz：/* FAQ */

2024-01-25T09:00:04Z

FAQ

←上一版本		2024年1月25日 (四) 09:00的版本
第173行：		第173行：
	HTTP/3 encrypts connections by default at the transport layer, offering improved security. This differs from previous versions, where encryption occurred separately at the application layer. Encrypting by default helps protect user data, reduces latency, and ensures a safer browsing experience.		HTTP/3 encrypts connections by default at the transport layer, offering improved security. This differs from previous versions, where encryption occurred separately at the application layer. Encrypting by default helps protect user data, reduces latency, and ensures a safer browsing experience.

			===Is HTTP client side connection pooling still valid when QUIC, HTTP/3 is the major/all traffic expected? ===

			It's still valid, because<ref>https://stackoverflow.com/questions/66182978/is-http-client-side-connection-pooling-still-valid-when-quic-http-3-is-the-majo</ref>:

			* a 0-RTT request is more computentionally expensive on both the client as well as the server side than just reusing the connection, since all private key crypto operations and certificate checks still apply
			* 0-RTT requests can introduce security issues due to providing a chance for replay attacks (see https://datatracker.ietf.org/doc/html/draft-ietf-quic-tls-34#section-9.2). Without using the 0-RTT feature a QUIC handshake still requires 1-RTT.

			However since QUIC already provides multiplexing multiple requests on a stream the client should not be required to keep a full pool of connections around. A single connection is typically sufficient, as long as the server advertises being able to support a high enough number of streams.

	[[Category:Network]]		[[Category:Network]]

2024年1月24日 (三) 07:59 Riguz

2024-01-24T07:59:51Z

←上一版本		2024年1月24日 (三) 07:59的版本
第4行：		第4行：
	* [https://http3-explained.haxx.se/en/ HTTP3 explained]		* [https://http3-explained.haxx.se/en/ HTTP3 explained]
	* [https://quicwg.org/ QUIC WorkingGroup]		* [https://quicwg.org/ QUIC WorkingGroup]

			[[Image:HTTP3 changes.webp\|600px]]<ref>https://ably.com/topic/http3</ref>

	[[Image:HTTP semantics.png\|300px]]<ref>https://nestify.io/blog/http-3-everything-you-need-to-know/</ref>		[[Image:HTTP semantics.png\|300px]]<ref>https://nestify.io/blog/http-3-everything-you-need-to-know/</ref>

Riguz：/* Browser support */

2024-01-24T02:53:02Z

Browser support

←上一版本		2024年1月24日 (三) 02:53的版本
第154行：		第154行：
	Firefox: set <syntaxhighlight lang="bash" inline>network.http.http3.enabled=true</syntaxhighlight> in about:config		Firefox: set <syntaxhighlight lang="bash" inline>network.http.http3.enabled=true</syntaxhighlight> in about:config

	Chrome:		Chrome(also need to disable cache):
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --enable-quic --origin-to-force-quic-on=localhost:443		/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --enable-quic --origin-to-force-quic-on=localhost:443

Riguz：/* Browser support */

2024-01-24T02:50:48Z

Browser support

←上一版本		2024年1月24日 (三) 02:50的版本
第150行：		第150行：
	* https://caniuse.com/http3		* https://caniuse.com/http3

	Chrome/Firefox ~~might not use HTTP3 even if~~ configured ~~correctly~~.<ref>https://www.smashingmagazine.com/2021/09/http3-practical-deployment-options-part3/</ref>		Chrome/Firefox need to be configured.<ref>https://www.smashingmagazine.com/2021/09/http3-practical-deployment-options-part3/</ref>

			Firefox: set <syntaxhighlight lang="bash" inline>network.http.http3.enabled=true</syntaxhighlight> in about:config

			Chrome:
			<syntaxhighlight lang="bash">
			/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --enable-quic --origin-to-force-quic-on=localhost:443
			</syntaxhighlight>

	= FAQ =		= FAQ =

Riguz：/* caddy */

2024-01-23T14:54:48Z

caddy

←上一版本		2024年1月23日 (二) 14:54的版本
第140行：		第140行：
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	caddy run		caddy run
			# if http3 somehow not working, try restart it
			# see: https://caddy.community/t/firefox-not-always-using-http-3/13755
	</syntaxhighlight>		</syntaxhighlight>

Riguz：/* quiche-server */

2024-01-23T14:42:27Z

quiche-server

←上一版本		2024年1月23日 (二) 14:42的版本
第110行：		第110行：
	content-length: 0		content-length: 0
	</syntaxhighlight>		</syntaxhighlight>

			Note: this could not be requested by browser.

	=== caddy ===		=== caddy ===

Riguz：/* caddy */

2024-01-23T11:41:38Z

caddy

←上一版本		2024年1月23日 (二) 11:41的版本
第134行：		第134行：
	}		}
	}		}
	</syntaxhighlight>		</syntaxhighlight><ref>https://caddyserver.com/docs/caddyfile/options#protocols</ref>

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">

Riguz：/* caddy */

2024-01-23T11:40:39Z

caddy

@@ 第118行： / 第118行： @@
 sudo mv caddy_darwin_arm64 /usr/local/bin/caddy
 </syntaxhighlight>
 == Browser support ==

Riguz：/* HTTP3 test sites */

2024-01-23T11:10:46Z

HTTP3 test sites

←上一版本		2024年1月23日 (二) 11:10的版本
第100行：		第100行：
	It's also possile to start a local server:		It's also possile to start a local server:

			=== quiche-server ===
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	cd quiche		cd quiche
第108行：		第109行：
	server: quiche		server: quiche
	content-length: 0		content-length: 0
			</syntaxhighlight>

			=== caddy ===
			Download caddy via https://caddyserver.com/download:

			<syntaxhighlight lang="bash">
			chmod +x caddy_darwin_arm64
			sudo mv caddy_darwin_arm64 /usr/local/bin/caddy
	</syntaxhighlight>		</syntaxhighlight>

HTTP/3 - 版本历史

Riguz：​/* Browser support */

Riguz：​/* FAQ */

2024年1月24日 (三) 07:59 Riguz

Riguz：​/* Browser support */

Riguz：​/* Browser support */

Riguz：​/* caddy */

Riguz：​/* quiche-server */

Riguz：​/* caddy */

Riguz：​/* caddy */

Riguz：​/* HTTP3 test sites */

Riguz：/* Browser support */

Riguz：/* FAQ */

Riguz：/* Browser support */

Riguz：/* Browser support */

Riguz：/* caddy */

Riguz：/* quiche-server */

Riguz：/* caddy */

Riguz：/* caddy */

Riguz：/* HTTP3 test sites */