elixir-mint / mint
91%
main: 91%

LAST BUILD BRANCH: http2-followups
DEFAULT BRANCH: main
Repo Added
Token xUOJjt5H7KcTvx6ikZQ7qWuMslrGKsjIE regen
Build 391 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 http2-followups
branch: SELECT
CHANGE BRANCH
x
Sync Branches

coverage: 90.656% (+0.1%) from 90.508%
Relevant lines Covered
2012 RELEVANT LINES 1824 COVERED LINES
717.74 HITS PER LINE
Source Files on main

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
ca7e4f44... http2-followups Document that pushed origins aren't checked RFC 9113 8.4 only lets a server push responses for origins it's authoritative for. Mint doesn't check the pushed :scheme and :authority, so the server push docs now say to compare them with the connecti... Pull #522 ericmj github
90.66
5d1d3ceb... v1.10 Release v1.10.2 push ericmj github
88.66
5c51742a... test-followups Generate transfer codings with chunked first and last in the HTTP/1 fuzz Responses with more than one transfer coding could come up, as a generated Transfer-Encoding: chunked plus a random Transfer-Encoding: gzip header, but no invariant compared... Pull #523 ericmj github
90.41
f707415a... http2-followups Treat a 204 response to CONNECT as an established tunnel The check for 204 and 304 responses, which must not have content, came before the check for 2xx responses to CONNECT. A CONNECT request answered with 204 was treated as a response without c... Pull #522 ericmj github
90.81
defd0a8c... http1-followups Fail requests pipelined behind a 101 response After a 101 response the connection stayed open with the queued requests in place, so bytes arriving later, which belong to the protocol the server switched to (RFC 9110 15.2.2), were parsed as HTTP/1... Pull #521 ericmj github
90.55
651b3cdd... http2-followups Treat a 204 response to CONNECT as an established tunnel The check for 204 and 304 responses, which must not have content, came before the check for 2xx responses to CONNECT. A CONNECT request answered with 204 was treated as a response without c... Pull #522 ericmj github
90.72
a6c9e499... test-followups Generate transfer codings with chunked first and last in the HTTP/1 fuzz The generated framing headers only used Transfer-Encoding: chunked, so the choice between chunked framing and reading until close was never exercised. Chunked bodies are now... Pull #523 ericmj github
90.46
7f422d71... http1-followups Fail requests pipelined behind a 101 response After a 101 response the connection stayed open with the queued requests in place, so bytes arriving later, which belong to the protocol the server switched to (RFC 9110 15.2.2), were parsed as HTTP/1... Pull #521 ericmj github
90.45
fb850d37... main Release v1.11.0 push ericmj github
90.51
2ec8b696... main Merge commit from fork * Use chunked framing only when chunked is the final transfer coding RFC 9112 section 6.3 defines the response body length by the last coding in Transfer-Encoding: chunked framing when chunked is final, otherwise read unti... push web-flow github
90.51
See All Builds (323)

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