HTTPS - 版本历史

Riguz：/* Implemention */

2024-01-24T08:10:58Z

Implemention

←上一版本		2024年1月24日 (三) 08:10的版本
第3行：		第3行：

	= Implemention =		= Implemention =
			HTTP/1.0 :

	[[Image:http-request-over-tcp-tls.png\|400px]]<ref>https://blog.cloudflare.com/http3-the-past-present-and-future</ref>		[[Image:http-request-over-tcp-tls.png\|400px]]<ref>https://blog.cloudflare.com/http3-the-past-present-and-future</ref>

			HTTP/3

			[[Image:http-request-over-quic.png\|400px]]

	= HTTP vs HTTPS =		= HTTP vs HTTPS =

Riguz：/* Implemention */

2024-01-24T08:08:43Z

Implemention

←上一版本		2024年1月24日 (三) 08:08的版本
第3行：		第3行：

	= Implemention =		= Implemention =
	[[Image:http-request-over-tcp-tls.png\|~~600px~~]]<ref>https://blog.cloudflare.com/http3-the-past-present-and-future</ref>		[[Image:http-request-over-tcp-tls.png\|400px]]<ref>https://blog.cloudflare.com/http3-the-past-present-and-future</ref>

	= HTTP vs HTTPS =		= HTTP vs HTTPS =

2024年1月24日 (三) 08:08 Riguz

2024-01-24T08:08:03Z

←上一版本		2024年1月24日 (三) 08:08的版本
第1行：		第1行：
	Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP).		Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP).
	The protocol is therefore also referred to as HTTP over [[TLS]], or HTTP over [[SSL]].		The protocol is therefore also referred to as HTTP over [[TLS]], or HTTP over [[SSL]].

			= Implemention =
			[[Image:http-request-over-tcp-tls.png\|600px]]<ref>https://blog.cloudflare.com/http3-the-past-present-and-future</ref>

	= HTTP vs HTTPS =		= HTTP vs HTTPS =

Riguz：/* Performance */

2024-01-21T03:48:58Z

Performance

←上一版本		2024年1月21日 (日) 03:48的版本
第38行：		第38行：
	== Performance ==		== Performance ==

	[[Image:http vs https.png\|600px]]		[[Image:http vs https.png\|600px]]<ref>https://www.httpvshttps.com/</ref>

	[[Image:http vs https vs http2.png\|600px]]		[[Image:http vs https vs http2.png\|600px]]<ref>https://www.tunetheweb.com/performance-test-360/</ref>

	== See also ==		== See also ==

Riguz：/* Performance */

2024-01-21T03:47:40Z

Performance

←上一版本		2024年1月21日 (日) 03:47的版本
第39行：		第39行：

	[[Image:http vs https.png\|600px]]		[[Image:http vs https.png\|600px]]

			[[Image:http vs https vs http2.png\|600px]]

	== See also ==		== See also ==

Riguz：/* HTTPs and HTTP/2 */

2024-01-21T02:53:20Z

HTTPs and HTTP/2

←上一版本		2024年1月21日 (日) 02:53的版本
第36行：		第36行：
	This means that in practice, '''the major performance benefits of HTTP/2 first require the use of HTTPS'''.		This means that in practice, '''the major performance benefits of HTTP/2 first require the use of HTTPS'''.

			== Performance ==

			[[Image:http vs https.png\|600px]]

	== See also ==		== See also ==

Riguz：/* HTTP vs HTTPS */

2023-12-06T09:56:30Z

HTTP vs HTTPS

←上一版本		2023年12月6日 (三) 09:56的版本
第15行：		第15行：

	Additionally, attackers can still analyze encrypted HTTPS traffic for “side channel” information. This can include the time spent on site, or the relative size of user input.		Additionally, attackers can still analyze encrypted HTTPS traffic for “side channel” information. This can include the time spent on site, or the relative size of user input.

			The domain name is not protected, this is primarily to support Server Name Indication ([[SNI]]), a TLS extension that allows multiple hostnames to be served over HTTPS from one IP address.


	== How difficult is it to attack an HTTPS connection?==		== How difficult is it to attack an HTTPS connection?==

Riguz：/* What information does HTTPS not protect? */

2023-12-06T09:53:58Z

What information does HTTPS not protect?

←上一版本		2023年12月6日 (三) 09:53的版本
第15行：		第15行：

	Additionally, attackers can still analyze encrypted HTTPS traffic for “side channel” information. This can include the time spent on site, or the relative size of user input.		Additionally, attackers can still analyze encrypted HTTPS traffic for “side channel” information. This can include the time spent on site, or the relative size of user input.

			== How difficult is it to attack an HTTPS connection?==

			Attacks on HTTPS connections generally fall into 3 categories:

			* Compromising the quality of the HTTPS connection, through cryptanalysis or other protocol weaknesses.
			* Compromising the client computer, such as by installing a malicious root certificate into the system or browser trust store.
			* Obtaining a “rogue” certificate trusted by major browsers, generally by manipulating or compromising a certificate authority.

			These are all possible, but for most attackers they are very difficult and require significant expense. Importantly, they are all targeted attacks, and are not feasible to execute against any user connecting to any website.

			By contrast, plain HTTP connections can be easily intercepted and modified by anyone involved in the network connection, and so attacks can be carried out at large scale and at low cost.

	== HTTPs and HTTP/2 ==		== HTTPs and HTTP/2 ==

Riguz：/* HTTPs and HTTP/2 */

2023-12-06T08:27:32Z

HTTPs and HTTP/2

←上一版本		2023年12月6日 (三) 08:27的版本
第20行：		第20行：

	This means that in practice, '''the major performance benefits of HTTP/2 first require the use of HTTPS'''.		This means that in practice, '''the major performance benefits of HTTP/2 first require the use of HTTPS'''.


			== See also ==

			* [https://http2.github.io/faq/\| HTTP2 FAQ]
			* [https://tools.ietf.org/html/rfc7540\| RFC7540: Hypertext Transfer Protocol Version 2 (HTTP/2)]


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

Riguz：/* HTTPs and HTTP/2 */

2023-12-06T08:25:08Z

HTTPs and HTTP/2

←上一版本		2023年12月6日 (三) 08:25的版本
第19行：		第19行：
	While [[HTTP/2]] does not require the use of encryption in its formal spec, every major browser that has implemented HTTP/2 has only implemented support for encrypted connections, and no major browser is working on support for HTTP/2 over unencrypted connections.		While [[HTTP/2]] does not require the use of encryption in its formal spec, every major browser that has implemented HTTP/2 has only implemented support for encrypted connections, and no major browser is working on support for HTTP/2 over unencrypted connections.

	This means that in practice, the major performance benefits of HTTP/2 first require the use of HTTPS.		This means that in practice, '''the major performance benefits of HTTP/2 first require the use of HTTPS'''.

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

HTTPS - 版本历史

Riguz：​/* Implemention */

Riguz：​/* Implemention */

2024年1月24日 (三) 08:08 Riguz

Riguz：​/* Performance */

Riguz：​/* Performance */

Riguz：​/* HTTPs and HTTP/2 */

Riguz：​/* HTTP vs HTTPS */

Riguz：​/* What information does HTTPS not protect? */

Riguz：​/* HTTPs and HTTP/2 */

Riguz：​/* HTTPs and HTTP/2 */

Riguz：/* Implemention */

Riguz：/* Implemention */

Riguz：/* Performance */

Riguz：/* Performance */

Riguz：/* HTTPs and HTTP/2 */

Riguz：/* HTTP vs HTTPS */

Riguz：/* What information does HTTPS not protect? */

Riguz：/* HTTPs and HTTP/2 */

Riguz：/* HTTPs and HTTP/2 */