Compression Dictionary Transport
The draft-ietf-httpbis-compression-dictionary-19 proposes a dictionary-based compression mechanism for HTTP, enhancing performance and reducing bandwidth, with guidelines for usage and negotiation, currently under evaluation for standardization.
Read original article
The document draft-ietf-httpbis-compression-dictionary-19 outlines a mechanism for dictionary-based compression in the Hypertext Transfer Protocol (HTTP). This approach allows clients and servers to reduce the size of transmitted data, enhancing performance and minimizing bandwidth usage. The draft extends existing HTTP compression methods and provides guidelines for the delivery and utilization of compression dictionaries. It specifies how designated HTTP responses can serve as external dictionaries for future responses, particularly for compression schemes like Brotli and Zstandard. The document also details the HTTP headers necessary for negotiating dictionary usage and registers content encoding values for these compression methods. Two primary use cases are highlighted: using a previous version of a resource as a dictionary for a newer version, and referencing an external dictionary for common content patterns across multiple resources. The draft is currently in the IESG evaluation stage and is intended for publication as a Proposed Standard.
- The draft specifies a mechanism for dictionary-based compression in HTTP.
- It aims to improve performance and reduce bandwidth consumption.
- It extends existing HTTP compression methods and provides negotiation guidelines.
- Two main use cases include version upgrades and common content compression.
- The document is under evaluation for publication as a Proposed Standard.
Related
Httpwtf?
HTTP has hidden features like cache directives, trailers for metadata, and 1XX codes. Websockets bypass CORS, X-* headers allow custom extensions. Despite quirks, HTTP is vital for client-server communication.
Understanding HTTP/3 – Features, Benefits and Impact
HTTP/3, utilizing QUIC for transport, enhances web performance and security with features like reduced latency, connection migration, and built-in encryption. Major browsers support it, requiring adaptation for developers and testers.
Y'all are sleeping on HTTP/3
HTTP/3, utilizing the QUIC protocol, now accounts for over 30% of web traffic, enhancing speed and reliability while addressing TCP limitations, though challenges in tooling and support persist.
Comparing HTTP/3 vs. HTTP/2 Performance (2020)
Cloudflare has launched HTTP/3, enhancing internet performance with UDP, reducing head-of-line blocking, and offering 0-RTT support. Over 113,000 zones have activated it, showing mixed real-world performance results.
Always support compressed response in an API service
Enabling compressed responses in API services reduces bandwidth costs and enhances user experience. Frameworks like Gin and Nginx facilitate gzip compression, making it a straightforward enhancement for web services.
8 commentsPre-shared compression dictionaries are rarely seen in the wild because they rarely provide meaningful benefit, particularly in the cases you care about most.
With something like that you could preload all of the most common libraries in the background.
I wonder what percentage of http traffic is redundant compression dictionaries. How much could this actually help in theory?
Great tech promising amazing efficiencies and speedups, but programmers are too lazy to use them correctly, so they see barely any use, and the few places it is used correctly are overshadowed by the few places it is used wrongly hurting performance.
Lesson: Tech that leads to the same page loading slightly faster generally won't be used unless they are fully automatic and enabled by default.
Http push required extra config on the server to decide what to push. This requires extra headers to determine what content to compress against (and the server to store that old/common content).
Neither will succeed because the vast majority of developers don't care about that last little bit of loading speed.
Related
Httpwtf?
HTTP has hidden features like cache directives, trailers for metadata, and 1XX codes. Websockets bypass CORS, X-* headers allow custom extensions. Despite quirks, HTTP is vital for client-server communication.
Understanding HTTP/3 – Features, Benefits and Impact
HTTP/3, utilizing QUIC for transport, enhances web performance and security with features like reduced latency, connection migration, and built-in encryption. Major browsers support it, requiring adaptation for developers and testers.
Y'all are sleeping on HTTP/3
HTTP/3, utilizing the QUIC protocol, now accounts for over 30% of web traffic, enhancing speed and reliability while addressing TCP limitations, though challenges in tooling and support persist.
Comparing HTTP/3 vs. HTTP/2 Performance (2020)
Cloudflare has launched HTTP/3, enhancing internet performance with UDP, reducing head-of-line blocking, and offering 0-RTT support. Over 113,000 zones have activated it, showing mixed real-world performance results.
Always support compressed response in an API service
Enabling compressed responses in API services reduces bandwidth costs and enhances user experience. Frameworks like Gin and Nginx facilitate gzip compression, making it a straightforward enhancement for web services.