Re: [fetch] Access to the HTTP trailer (#34)

@mcmanus not sure I follow.. AFAIK, per spec the server can't reply with same ID? Say I have...

- Client request: `{id: 5, path: /thing}`
- Server issues PUSH_PROMISE: `{id: 6, path: /.well-known/trailers, body: some-json-thing}`

We can't use the same path for all trailers since that'd clash with existing caching logic and streams would trample over each other. How do we tie these streams together? Assuming that's resolved, looking up trailers would require a separate cache lookup? Or, do you have something different in mind?


---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/34#issuecomment-123386602