• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

elixir-mint / mint
91%
main: 91%

Build:
Build:
LAST BUILD BRANCH: push-promise-authority
DEFAULT BRANCH: main
Repo Added 11 Jun 2022 07:10AM UTC
Token xUOJjt5H7KcTvx6ikZQ7qWuMslrGKsjIE regen
Build 416 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: http2-followups
CHANGE BRANCH
x
Reset
Sync Branches
  • http2-followups
  • al/1.18
  • al/bump-ci
  • al/ci
  • al/client-settings
  • al/deps
  • al/elixir-1.10
  • al/elixir-1.11+
  • al/fix-leak
  • al/fix-tests
  • al/http2-logs
  • al/improve-defguard
  • al/modernize-ci
  • al/stream-docs
  • al/update-ci-versions
  • al/updates
  • allow-not-validating-target
  • allow_302_for_twitter_integration_test
  • andrea/code-coverage
  • andrea/dialyzer
  • andrea/fix-guard
  • andrea/new-ci-versions
  • apply-http2-client-settings
  • check-http2-content-length
  • chore/replace-deprecated-xref-exclude
  • ci-pin-ubuntu-otp24
  • clamp-tunnel-timeout
  • close_sockets_on_error
  • comp-time-optimization
  • configurable-test-ports
  • connect-tunnel-fixes
  • connection-docs-ref
  • contributing-and-testing-housekeeping
  • dialyzer-without-ignore-file
  • docs-for-open
  • dont-close-socket-on-recv-timeout
  • ericmj/deprecate-read-write
  • ericmj/fix-1xx-informational-response
  • ericmj/http2-connection-window-size
  • ericmj/http2-larger-default-windows
  • ericmj/inet4-option
  • ericmj/local-h2c-integration-tests
  • ericmj/support-elixir-1.12
  • ericmj/update-ubuntu
  • fix-cannot-build-docker-image-using-podman-compose
  • fix-dialyzer
  • fix-http1-tests-not-tagged-correctly
  • fix-incorrect-ci-badge
  • fix-warnings
  • fix/446-proxy-host-header
  • fix/http10-connect-tunnel
  • fix/http2-validate-request-fields
  • fix/humize_error_code_custom_error
  • forward-proxy-mode
  • fuzz-http1-mid-scenario-requests
  • fuzz-http1-transfer-codings
  • fuzz-http2-close-listen-socket
  • fuzz-http2-connect-tunnel
  • fuzz-http2-connection-window
  • http-fuzz-properties
  • http1-1xx-close
  • http1-empty-te
  • http1-followups
  • http1-header-parsing
  • http1-line-size-limit
  • http1-pipelining
  • http1-reason-phrase
  • http1-rfc9112-body-rules
  • http1-te-parameters
  • http1-upgrade-pipelined
  • http2-connect-204
  • http2-connect-target
  • http2-frame-validation
  • http2-header-block-bound
  • http2-header-list-size-docs
  • http2-push-origin-docs
  • http2-push-target-validation
  • http2-remove-infinity-branches
  • http2-response-semantics
  • http2-server-push
  • https-tunnel-proxies
  • ignore-http2-window-update-on-closed-streams
  • ip-address-match-fun
  • ipv6-host-header
  • jv-default-store
  • jv-elixir-1-19
  • keep-http1-state-after-pipelined-responses
  • main
  • next_body_chunk
  • np/export-error-types
  • optimize-http/2-request-creation
  • patch-3
  • preserve_header_case
  • push-promise-authority
  • pvthuyen/add-support-for-cacerts-get
  • refs/heads/main
  • refs/pull/399/merge
  • refs/pull/407/merge
  • refs/pull/500/merge
  • return-responses-in-parse-order
  • rewrite-contributing-and-testing-doc
  • run-ci-against-erlang-27.1
  • stream-http1-headers
  • test-followups
  • test-http2-interim-no-101
  • tunnel-target-identity
  • unnecessary-rst-stream-2
  • unsafe-proxy-opts
  • update-deps
  • use-hpax-protocol-resize
  • use_local_http_bin_in_all_tests
  • v1.10
  • validate-http2-response-headers
  • whatyouhide/issue311
  • wm-decompression
  • wm-docker-compose
  • wm-recv-response
  • wrap-tunnel-errors

02 Oct 2026 10:00PM UTC coverage: 90.656% (+0.1%) from 90.508%
ca7e4f4473b413622bf609a9e0cfa2c833e8efe2-PR-522

Pull #522

github

ericmj
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 connection's
origin before using a pushed response and to cancel the promised request
with cancel_request/2 if they don't match.

The example of promised headers also lists :scheme and :authority, which
promised requests always include.
Pull Request #522: Fix HTTP/2 header block bound, push validation and CONNECT 204

52 of 54 new or added lines in 1 file covered. (96.3%)

2 existing lines in 2 files now uncovered.

1824 of 2012 relevant lines covered (90.66%)

717.74 hits per line

Relevant lines Covered
Build:
Build:
2012 RELEVANT LINES 1824 COVERED LINES
717.74 HITS PER LINE
Source Files on http2-followups
  • Tree
  • List 22
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

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 02 Oct 2026 10:01PM UTC ericmj github
90.66
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 28 Sep 2026 03:02PM UTC ericmj github
90.81
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 28 Sep 2026 01:30PM UTC ericmj github
90.72
See All Builds (348)

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.

Could not find badge in README.

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
  • Settings
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc