Skip to content

reverseproxy: Only handle extended connect for websockets#6740

Merged
mholt merged 1 commit intocaddyserver:masterfrom
bt90:patch-1
Dec 11, 2024
Merged

reverseproxy: Only handle extended connect for websockets#6740
mholt merged 1 commit intocaddyserver:masterfrom
bt90:patch-1

Conversation

@bt90
Copy link
Contributor

@bt90 bt90 commented Dec 10, 2024

RFC 8441 specifies that:

The :protocol pseudo-header field MUST be included in the CONNECT request, and it MUST have a value of "websocket" to initiate a WebSocket connection on an HTTP/2 stream

Otherwise we might end up modifying other use cases of the extended CONNECT method later on.

@bt90
Copy link
Contributor Author

bt90 commented Dec 10, 2024

@WeidiDeng

@WeidiDeng
Copy link
Member

LGTM, :shipit:

@bt90
Copy link
Contributor Author

bt90 commented Dec 11, 2024

@mholt

Copy link
Member

@mholt mholt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent, thank you! I mainly wanted @WeidiDeng 's approval first 😄

@mholt mholt merged commit 328fb61 into caddyserver:master Dec 11, 2024
@mholt mholt added the bug 🐞 Something isn't working label Dec 11, 2024
@mholt mholt added this to the v2.9.0-beta.4 milestone Dec 11, 2024
mohammed90 pushed a commit to cedricziel/caddy that referenced this pull request Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug 🐞 Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants