Re: [whatwg/fetch] Consider removing trailers API (#772)

I started implementing trailers in `async-http` and `http-protocol`. At face value it's not a very nice abstraction. It's not well supported by HTTP/1 since it can only be used with chunked transfer. It's the first thing I've encountered which has a significant semantic difference at the high level across HTTP versions. I'd be interested to hear more about how this should be implemented. For example, if user specifies a fixed length body, should we convert it to chunked encoding if the user also provides trailers?

-- 
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/issues/772#issuecomment-450227556