Re: [whatwg/fetch] Add compression dictionary negotiation and decoding to the fetch processing model (Issue #1739)

I'm working on a PR for Fetch now that incorporates the IETF draft. Looking at it, there are two paths I can take.

1. Add steps to [HTTP-network fetch](https://fetch.spec.whatwg.org/#http-network-fetch) to:
    - select a dictionary partitioning key
    - turn dictionary storage off for navigation requests
    - turn off dictionary support for opaque requests
    - fail opaque responses that used dictionaries
    - and then defer to the IETF document for the processing as part of step 7.5 (and include the dictionary spec)
3. Add a new `HTTP-network-dictionary fetch` step between [HTTP-network-or-cache fetch](https://fetch.spec.whatwg.org/#http-network-or-cache-fetch) and [HTTP-network fetch](https://fetch.spec.whatwg.org/#http-network-fetch) that does all of the dictionary matching and storage. The content coding would still happen transparently but all of the processing steps for managing the dictionaries themselves would be in fetch.

Option 2 would spell things out directly but would be duplicating a lot of the IETF draft (and require keeping both in sync as any errata or modifications are made).

@annevk do you have a preference for one over the other?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1739#issuecomment-2323400781
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1739/2323400781@github.com>