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

Yes, we need to discuss that point. /cc @domenic

Like the headers being atomic, my gut feeling is that the trailers should also be handled without backpressure once the body has been consumed. So, you may need to wait for completion of body consumption by the ReadableStream due to backpressure, or it's ok that a UA fulfills the trailer promise without waiting for completion of consumption if possible.

> not distinct

https://tools.ietf.org/html/rfc7230#section-4.1.2 says

```
   When a chunked message containing a non-empty trailer is received,
   the recipient MAY process the fields (aside from those forbidden
   above) as if they were appended to the message's header section.
```

Not fully sure, but I interpret this as it doesn't forbid distinction between headers and trailers at the application level.

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