elixir-mint / mint

91%

main: 90%

LAST BUILD ON BRANCH http2-connect-204

branch: http2-connect-204

CHANGE BRANCH

x

Reset

Sync Branches

• http2-connect-204
• 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
• 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-target
• http2-followups
• 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
• 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

Build # f707415a1199ec76812b001925841af938bb7478-PR-535

Build Type

Pull #535

github

Committed by ericmj

Commit Message

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 content, so the
first DATA frame on the tunnel failed the request with a protocol error.

RFC 9110 9.3.6 and RFC 9113 8.5 make any 2xx response to CONNECT
establish a tunnel, so the CONNECT case is checked first and DATA
frames after a 204 are delivered as tunnel data.

Pull Request Pull Request #535: Treat a 204 response to CONNECT as an established tunnel

Coverage Stats

1 of 1 new or added line in 1 file covered. (100.0%)

4 existing lines in 2 files now uncovered.

1823 of 2012 relevant lines covered (90.61%)

726.27 hits per line