SOCKS Authentication fails for CONNECT if username contains special characters #548
Labels
backend
Issues related to the platform backend.
bug
Something isn't working.
medium priority
Medium priority issues to be done in a couple of sprints.
t-platform
Issues with this label are in the ownership of the platform team.
validated
Issues that are resolved and their solutions fulfill the acceptance criteria.
SOCKS authentication fails for CONNECT requests when the username contains a
@
:For a HTTP request, everything works as expected (the username is sent as-is).
For a HTTPS / CONNECT request, the username sent to the upstream SOCKS5 proxy is URL escaped (e.g.
foo%40bar.baz
, as seen in a packet capture) and the SOCKS authentication request fails due to incorrect credentials, the proxy returns a597
error.The text was updated successfully, but these errors were encountered: