Re: [whatwg/fetch] Add trailer support to network responses (#344)

`TE: trailers` isn't a terribly useful signal for fetch to generate, because it doesn't tell the server whether individual headers are going to be actually processed (e.g., `ETag` and `Last-Modified` for a cache). 

What it does help with is determining whether an entire *path* is compatible with trailers; i.e., whether or not there's a HTTP/1.0 hop. So it make sense for intermediaries to generate it when the downstream path is trailer-safe, *or* the intermediary buffers responses and sticks them into headers. 

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