You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just to make sure I am on the right track, I think what I should do is implement the TE struct using the header! macro, passing the QualityItem<Encoding> struct as this also has a notion of quality values, adding the Trailer variant to the Encoding enum and adding it to the related impls, and then writing the documentation based off of RFC7230. Does this make sense or am I missing something?
The `TE` header is used by a client to specify which
transfer encodings other than `chunked` it will accept.
It also specifies whether HTTP trailers are acceptable.
This commit also adds a `Trailers` variant to the
`hyper::header::shared::Encoding` enum.
Closeshyperium#1109
BREAKING CHANGE: The `Encoding` enum has an additional
variant, `Trailers`.
The TE header field is similar to Accept-Encoding, but for the Transfer-Encoding instead of the Content-Encoding
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/TE
Section 14.39 https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
The text was updated successfully, but these errors were encountered: