Skip to content

fix core: use peer address for websocket client connections - #1276

Closed
seriouscoder43 wants to merge 2 commits into
userver-framework:developfrom
seriouscoder43:fix-ws
Closed

fix core: use peer address for websocket client connections#1276
seriouscoder43 wants to merge 2 commits into
userver-framework:developfrom
seriouscoder43:fix-ws

Conversation

@seriouscoder43

Copy link
Copy Markdown
Contributor

MakeWebsocketConnection() incorrectly uses Getsockname() to save the remote peer. Then connection's RemoteAddr() becomes always wrong

@apolukhin

Copy link
Copy Markdown
Member

LGTM

@apolukhin apolukhin closed this Aug 9, 2026
@apolukhin apolukhin reopened this Aug 9, 2026
@apolukhin

Copy link
Copy Markdown
Member

LGTM

@apolukhin apolukhin closed this Aug 11, 2026
@apolukhin apolukhin reopened this Aug 11, 2026
@apolukhin

Copy link
Copy Markdown
Member

LGTM

@robot-magpie

robot-magpie Bot commented Aug 11, 2026

Copy link
Copy Markdown

Many thanks for the PR! @apolukhin is now importing your pull request into our internal upstream repository.

@robot-magpie

robot-magpie Bot commented Aug 11, 2026

Copy link
Copy Markdown

✅ This pull request is being closed because it has been successfully merged into our internal monorepository.
Your changes will be pushed to this repository soon. Thank you for your contribution!

@robot-magpie robot-magpie Bot closed this Aug 11, 2026
robot-piglet pushed a commit that referenced this pull request Aug 11, 2026
MakeWebsocketConnection() incorrectly uses Getsockname() to save the remote peer. Then connection's RemoteAddr() becomes always wrong

---

Pull Request resolved: #1276

Co-authored-by: Antony Polukhin <antoshkka@gmail.com>
commit_hash:58f1216f00993df5fa32023535fca906e7db37bb
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.

2 participants