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

@sleevi fwiw, I don't think I am ignoring the raised concerns... As I noted before, existing implementations already "handle" trailers: we don't error out when we see them, we simply drop them on the floor. As such, if we add further carveouts that such metadata doesn't make into the HTTP cache (i.e. existing behavior), or affects the actual processing in any other way, what other implementation concerns do we have? 

As @annevk mentioned, the only thing we're asking for here is that the trailers are parsed and exposed in a new map on the response object. 

@mcmanus how would that work? Would I push a same-URL resource as the parent (err?) with headers at the end? 

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