Skip to content

encode: write status immediate for success response for CONNECT requests#6738

Merged
mholt merged 5 commits intomasterfrom
encode-connect
Dec 11, 2024
Merged

encode: write status immediate for success response for CONNECT requests#6738
mholt merged 5 commits intomasterfrom
encode-connect

Conversation

@WeidiDeng
Copy link
Member

fix 6733.

@WeidiDeng WeidiDeng requested a review from mholt December 8, 2024 12:52
…uest as success if status is not set explicitly
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.

Amazing Weidi, thank you for going down the rabbit hole on this one.

@mholt mholt merged commit bcaa8aa into master Dec 11, 2024
@mholt mholt deleted the encode-connect branch December 11, 2024 18:15
@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
…sts (caddyserver#6738)

* encode: write status immediate for success response for CONNECT requests

* fix compile

* fix test

* fix lint

* treat first write and flush for encode response writer to CONNECT request as success if status is not set explicitly
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.

reverse_proxy: h2 websocket stuck if client needs to send the first message and encode is enabled

3 participants