Skip to content

Conversation

metcoder95
Copy link
Member

This relates to...

Closes #4086

Rationale

Do we see a potential harm of this? I know the original idea was to tell the queue not to re-use the socket so it can be used by the caller instead.

From tests, everything seems normal, but wondering if there's something possibly that I'm not seeing to not do it.

Changes

Features

Bug Fixes

Breaking Changes and Deprecations

Status

@metcoder95 metcoder95 requested review from mcollina and ronag April 1, 2025 06:37
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

this is not enough to close that, as one header is missing. A test should also be added for that specific case.

@metcoder95 metcoder95 requested a review from mcollina April 21, 2025 11:12
@metcoder95 metcoder95 changed the title feat(#4086): keep alive on CONNECT feat(#4086): proxy keep alive Apr 25, 2025
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm

@metcoder95 metcoder95 merged commit 032d200 into main Jun 25, 2025
34 of 37 checks passed
@metcoder95 metcoder95 deleted the feat/4086 branch June 25, 2025 10:35
@github-actions github-actions bot mentioned this pull request Jun 26, 2025
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.

Support proxy keep-alive

2 participants