You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Our Zscaler proxy requires @ to be used within the username. Because the username and password are specified as part of a URL, they must be URL-encoded by the caller; otherwise consider what would happen if the user's password or username contained an @ or a :, etc.
To Reproduce
Steps to reproduce the behavior:
Self-hosted runner with http_proxy and https_proxy setup with user@name:password@proxy_url:proxy_port
For URL encoding. The @ within http_proxy and https_proxy will be replaced with %40 for URL encoding
http-client load the username as plain text without decoding
Expected behavior
Expect http-client decode username and password when needed.
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
Our Zscaler proxy requires
@
to be used within the username. Because the username and password are specified as part of a URL, they must be URL-encoded by the caller; otherwise consider what would happen if the user's password or username contained an @ or a :, etc.To Reproduce
Steps to reproduce the behavior:
http_proxy
andhttps_proxy
setup withuser@name:password@proxy_url:proxy_port
@
within http_proxy and https_proxy will be replaced with%40
for URL encodinghttp-client
load the username as plain text without decodingExpected behavior
Expect http-client decode username and password when needed.
Screenshots
The text was updated successfully, but these errors were encountered: