Repository navigation
Preserve custom Host headers for WebSocket requests - #6172
Merged
stamparm merged 1 commit intoNov 4, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For WebSocket targets,
--hostand Host headers supplied through--headersare discarded before the handshake. A scan against a virtual host therefore uses the URL's host instead.Pass explicit Host overrides to the WebSocket client while retaining its existing default Host generation. The regression test covers configured headers, per-request overrides, header files, auxiliary headers, and the default case.
Tests:
test_replication. Its six SQLite teardown errors also reproduce on unmodified master.git diff --checkpassed.