trillium-client-v0.1.1
·
1080 commits
to main
since this release
trillium-client-v0.1.1
jbr
Jacob Rothstein
This tag was signed with the committer’s verified signature.
jbr
Jacob Rothstein
trillium-client v0.1.1 resolves #79
Prior to this release, trillium client (and therefore also trillium-proxy) did not correctly abide by rfc7230§3.3.2, in that HEAD, 204, and 304 responses were not treated distinctly from other methods and response codes. As of this release, all server responses to HEAD requests and all responses that are 204 or 304 are assumed (per spec) to have zero length bodies, whether or not a content-length: 0 header is provided.