Skip to content

HTTP

Jump to bottom
HOA PHAN edited this page Dec 4, 2023 · 4 revisions

#http1 vs http2

There can be cases where HTTP/1.1 outperforms HTTP/2 depending on the specific circumstances. Some examples of when HTTP/1.1 may outperform HTTP/2 are:

Low Latency Networks: HTTP/1.1 may perform better on networks with low latency. This is because the benefits of HTTP/2's multiplexing and header compression are less significant when network latency is low.

Small Payloads: HTTP/1.1 may perform better than HTTP/2 for very small payloads. This is because HTTP/2's overhead for establishing a connection and compressing headers can outweigh the benefits of multiplexing for small payloads.

Limited Resources: HTTP/1.1 may perform better on devices with limited resources such as mobile devices. This is because HTTP/2's multiplexing and header compression require more resources than HTTP/1.1.

However, it's worth noting that these scenarios are relatively rare and HTTP/2 generally outperforms HTTP/1.1 in most cases.

#http1 vs http2 - cont

In general, HTTP/2 is a more efficient protocol than HTTP/1.1, and it can provide significant performance improvements for many types of web traffic. However, there are some cases where HTTP/1.1 can outperform HTTP/2. For example, HTTP/1.1 can be faster for small requests that do not require multiple resources. Additionally, HTTP/1.1 can be more efficient for requests that are made over a slow connection.

Here are some specific examples where HTTP/1.1 can outperform HTTP/2:

When the request is for a small file, such as an image or a CSS file.
When the request is made over a slow connection, such as a mobile network.
When the request is made to a server that does not support HTTP/2.
In general, HTTP/2 is the better choice for most web traffic. However, there are some cases where HTTP/1.1 can be a better option. If you are not sure which protocol to use, you can test both protocols and see which one provides better performance for your specific needs.

#http1 vs http3 https://github.com/reactor/reactor-netty/issues/2151

https://aws.amazon.com/about-aws/whats-new/2022/08/amazon-cloudfront-supports-http-3-quic/

https://blog.apnic.net/2023/09/25/why-http-3-is-eating-the-world/

https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/

eye

eye

Clone this wiki locally