elixir-mint / mint
91%
main: 90%

LAST BUILD BRANCH: fix/http2-validate-request-fields
DEFAULT BRANCH: main
Repo Added
Token xUOJjt5H7KcTvx6ikZQ7qWuMslrGKsjIE regen
Build 412 Last
Files 22
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH http1-empty-te
branch: http1-empty-te
CHANGE BRANCH
x
Sync Branches

coverage: 90.514% (+0.05%) from 90.46%
33d12943b099acaa8f3327a621a494510fc5b82b-PR-526

Pull #526

github

ericmj 
Treat an empty Transfer-Encoding list as no transfer codings

A Transfer-Encoding field with no list elements, such as an empty value
or ",", failed the response with :empty_token_list and closed the
connection. For a response to HEAD this happened before the rule that
such a response has no body, and a comma-only field between two
nonempty Transfer-Encoding fields failed the response instead of being
ignored.

RFC 9110 5.6.1 allows a #transfer-coding list with zero elements, so
such a field now adds no transfer coding when the framing is chosen. A
response with only an empty Transfer-Encoding and no Content-Length has
no framing, so its body is read until the connection closes (RFC 9112
6.3). The field still counts as present: with Content-Length it's an
error, and it makes an HTTP/1.0 response, including a 1xx one, close
the connection (RFC 9112 6.1).

Transfer-Encoding values are parsed only where they decide the framing,
combined into one value as on the request side, so a malformed value no
longer fails a response to HEAD, a 204 or 304 response, or a 2xx
response to CONNECT, whose Transfer-Encoding RFC 9110 9.3.6 says to
ignore. Where it does fail, the error comes after the :headers event
(with :stream_headers the field itself can be emitted first) and not
while the header section is incomplete, other header errors in the same
section are reported instead of it, and with Content-Length the error is
:transfer_encoding_and_content_length instead of {:invalid_token_list,
value}.

On the request side, a Transfer-Encoding field with no codings passed to
request/5 with a streamed body counts as no codings: when chunked is
appended to such a last field it replaces the empty value.
Pull Request #526: Treat an empty Transfer-Encoding list as no transfer codings

9 of 9 new or added lines in 2 files covered. (100.0%)

1 existing line in 1 file now uncovered.

1813 of 2003 relevant lines covered (90.51%)

712.93 hits per line

Relevant lines Covered
2003 RELEVANT LINES 1813 COVERED LINES
712.93 HITS PER LINE
Source Files on http1-empty-te

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
33d12943... http1-empty-te Treat an empty Transfer-Encoding list as no transfer codings A Transfer-Encoding field with no list elements, such as an empty value or ",", failed the response with :empty_token_list and closed the connection. For a response to HEAD this happene... Pull #526 ericmj github
90.51
See All Builds (344)

Badge your Repo: mint

We detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

Refresh