Repository navigation
Fix websocket proxy auth with colon in password - #2740
tilakraj-hub wants to merge 1 commit into
Conversation
|
|
|
Welcome @tilakraj-hub! |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tilakraj-hub The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
075cadd to
f857da4
Compare
|
Thanks for the PR @tilakraj-hub! Issue #2734 is already being addressed by earlier PR #2738, which also adds unit test coverage in ws_client_test.py and guards against IndexError when credentials lack a colon. Closing as duplicate in favor of #2738. |
|
@roycaihw Thank you for reviewing my PR and for the clarification. I understand that this issue is already being addressed by PR #2738. |
|
Thanks for your interest in contributing @tilakraj-hub! Glad to see your CNCF CLA is now sorted out. If you're looking for issues to tackle, a few good places to start:
Feel free to join the |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fixes websocket proxy authentication when the proxy password contains a colon (
:).Previously, proxy credentials were parsed using
split(':'), which caused passwords containing colons to be truncated. This change usessplit(':', 1)so the credentials are split only at the username/password separator and the complete password is preserved.Which issue(s) this PR fixes:
Fixes #2734
Special notes for your reviewer:
The change is limited to the proxy authentication credential parsing in
websocket_proxycare().The reported issue was reproduced before the fix and verified after the change with a password containing multiple colons.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs, usage docs, etc.: