Skip to content

Don't hardcode HTTP/2 in server responses - #279

Merged
vlovgr merged 3 commits into
mainfrom
fix-response-http-version
Oct 16, 2026
Merged

vlovgr merged 3 commits into
mainfrom
fix-response-http-version

Conversation

@vlovgr

@vlovgr vlovgr commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

Fixes #278. Note the point here is not HTTP/1.1 support, but rather that a server should not put a version different from the transport.

@vlovgr
vlovgr merged commit dc20a9e into main Oct 16, 2026
20 checks passed
@vlovgr
vlovgr deleted the fix-response-http-version branch October 16, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Server responses hardcode HttpVersion.HTTP/2, producing malformed HTTP/1.1 replies that strict clients reject

1 participant