Re: [whatwg/fetch] Trailer support in the API (#981)

> > Caching: not sure. Perhaps cached entries never have trailers?
> 
> [RFC9111](https://httpwg.org/specs/rfc9111.html#storing.fields):
> 
> > Caches MAY either store trailer fields separate from header fields or discard them. Caches MUST NOT combine trailer fields with header fields.

Not having consistent behavior between browsers there sounds like a recipe for incompatibilities.  If support for trailers is added to the web platform, I think the fetch spec needs to be clear on how browsers should handle that, even if caching proxies can behave differently (which also sounds like a major problem to me - as does caching proxies that never had to support them before potentially ignoring trailers, though guess the increased prevalence of HTTPS should mitigate that).

The Chrome networking team has historically pushed back pretty strongly on adding trailers because it's a pretty massive change to network APIs - a ton of stuff interposes on network requests in browsers, and much of it would need to be updated.  Has that changed?  That obviously doesn't mean work here shouldn't proceed, but it's a consideration if the goal here is broad adoption.

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

Message ID: <whatwg/fetch/issues/981/1743176449@github.com>