Compression Dictionary Transport #160
Labels
from: Google
Proposed, edited, or co-edited by Google.
position: support
topic: fetch
Relates to the Fetch API
topic: http
Spec relates to the HTTP (Hypertext Transfer Protocol) family of protocols
topic: loading
topic: networking
venue: WICG
Proposal is incubated in the Web Incubator Community Group
Request for position on an emerging web specification
Information about the specification
Design reviews and vendor positions
Anything else we need to know
Chrome Status Page: https://chromestatus.com/feature/5124977788977152
Example compression gains over Brotli: https://github.com/WICG/compression-dictionary-transport/blob/main/examples.md
It's still very early in the standards process but it will likely span the IETF HTTP working group and WHATWG HTML and Fetch standards and we wanted to bring the relevant parties together sooner rather than later to hash out the designs.
Compression dictionary transport provides a mechanism for websites to use existing resources in their cache as compression dictionaries for future requests. The key points are:
The flow as it currently stands is (generally):
use-as-dictionary:
response header that specifies the path matching rules for fetches where the dictionary would be applied (either for different versions of the same js/css/wasm/etc resource or a path spec for html pages where a stand-alone dictionary would be applied).sec-available-dictionary:
request header with the hash of the dictionary with the most specific match for the request. It also includes the dictionary compression algorithms it understands. i.e.Accept-Encoding: sbr,...
.Content-Encoding: sbr
andVary: Accept-Encoding,Sec-Available-Dictionary
The text was updated successfully, but these errors were encountered: