Stacks on #554 — the diff will show that commit too until it merges. ## Motivation `isValidPseudoHeaderValue` rejects CR, LF and NUL, which is narrower than the HTTP/1.1 request line actually needs. `:path` ends up as the request-target in: ``` METHOD SP request-target SP HTTP-version CRLF ``` so `:path = "/a HTTP/1.1"` serializes to `GET /a HTTP/1.1 HTTP/1.1`. Whether a recipient reads the first or the last SP-delimited token as the version decides what the request-target actually is, which is the usual parser-differential setup. RFC 9112 § 3.2 wants SP in a request-target percent-encoded, and bare HTAB and the other CTLs aren't valid there either. None of the HTTP/2 pseudo-headers have a grammar that allows SP or a CTL: `:method` and `:protocol` are tokens, `:scheme` is a URI scheme, `:authority` is host[:port], `:path` is a request-target, `:status` is 3DIGIT. So rejecting them doesn't reject anything well-formed. Same severity caveat as #554: NIOHTTP1's `uriOnlyContainsAllowedCharacters` already rejects SP in a request-target by default, so this is hardening rather than something exploitable on a stock pipeline. ## Modifications `isValidPseudoHeaderValue` goes from `{0x00, 0x0A, 0x0D}` to `<= 0x20 || == 0x7F`, so the whole CTL range plus SP and DEL. Bytes >= 0x80 stay allowed on purpose. They aren't delimiters in a request line or header block, and rejecting them would break anyone sending unencoded UTF-8 in `:path`. ### One behaviour change worth flagging `validateRequestBlock` runs on send as well as receive, so a client passing a URI with a raw space in it will now throw where it didn't before. I'd argue that's the right outcome, since NIOHTTP1's validator already rejects that URI by default and this makes the two layers agree, but it is a behaviour change and it's the bit most likely to need discussion. That's why I split it out of #554 instead of bundling them. ## Result Pseudo-header values containing SP or any control character are rejected. ## Testing Added to `HTTP2FramePayloadToHTTP1CodecCRLFTests.swift`: - `:path` with SP (`/a HTTP/1.1`), HTAB, VT, FF, DEL, SOH - SP in `:authority`, `:method`, `:scheme` - covered at the predicate, request-validation and server-codec levels The existing positive cases in that file still pass untouched — `/`, `/foo/bar`, `/foo?q=1&r=2`, `/foo#fragment`, `*`, `/foo%20bar`, `200` — which is the check that this doesn't reject anything legitimate. Built and ran on Linux, Swift 6.1 aarch64. `swift test -Xswiftc -warnings-as-errors` is clean with no new warnings, the new tests pass, and `swift format lint --strict Sources/ Tests/` is clean. --------- Co-authored-by: George Barnett <gbarnett@apple.com>
SwiftNIO HTTP/2
This project contains HTTP/2 support for Swift projects using SwiftNIO. To get started, check the API docs.
Building
swift-nio-http2 is a SwiftPM project and can be built and tested very simply:
$ swift build
$ swift test
Versions
Just like the rest of the SwiftNIO family, swift-nio-http2 follows SemVer 2.0.0 with a separate document declaring SwiftNIO's Public API.
swift-nio-http2 1.x
swift-nio-http2 versions 1.x are a pure-Swift implementation of the HTTP/2 protocol for SwiftNIO. It's part of the SwiftNIO 2 family of repositories and does not have any dependencies besides swift-nio and Swift 5. As the latest version, it lives on the main branch.
To depend on swift-nio-http2, put the following in the dependencies of your Package.swift:
.package(url: "https://github.com/apple/swift-nio-http2.git", from: "1.19.2"),
The minimum Swift version supported for SwiftNIO HTTP/2 releases are detailed below:
| SwiftNIO HTTP/2 | Minimum Swift Version |
|---|---|
1.0.0 ..< 1.18.0 |
5.0 |
1.18.0 ..< 1.21.0 |
5.2 |
1.21.0 ..< 1.23.0 |
5.4 |
1.24.0 ..< 1.27.0 |
5.5.2 |
1.27.0 ..< 1.29.0 |
5.6 |
1.29.0 ..< 1.31.0 |
5.7 |
1.31.0 ..< 1.37.0 |
5.8 |
1.37.0 ..< 1.39.0 |
5.9 |
1.39.0 ..< 1.43.0 |
6.0 |
1.43.0 ..< |
6.1 |
swift-nio-http2 0.x
The legacy swift-nio-http 0.x is part of the SwiftNIO 1 family of repositories and works on Swift 4.1 and newer but requires nghttp2 to be installed on your system. The source code can be found on the nghttp2-support-branch.
Developing SwiftNIO HTTP/2
For the most part, SwiftNIO development is as straightforward as any other SwiftPM project. With that said, we do have a few processes that are worth understanding before you contribute. For details, please see CONTRIBUTING.md in this repository.