When attempting to set an https_proxy where the proxy URL itself uses HTTPS, such as an AWS global accelerator, the process times out. Judging from strace() output, the client does not attempt to negotiate TLS, and instead sends plaintext HTTP to the proxy, which ignores it until the process times out.
Reproduction:
$ pro config set https://user:<email address hidden>:443/
* times out and fails
Expected result:
* Configures a working proxy for subsequent pro client commands
Notes:
* was only tested with an AWS GA instance
* a similar "curl -x {same-proxy-URI} {website}" works as expected.
* a similar "wget" with $ENV{https_proxy} set also times out.
* pro-client team has an example proxy URI with credentials that exhibits this behavior, but I'll try to come up with another reproducer for that end as well.
When attempting to set an https_proxy where the proxy URL itself uses HTTPS, such as an AWS global accelerator, the process times out. Judging from strace() output, the client does not attempt to negotiate TLS, and instead sends plaintext HTTP to the proxy, which ignores it until the process times out.
Reproduction: /user:<email address hidden>:443/
$ pro config set https:/
* times out and fails
Expected result:
* Configures a working proxy for subsequent pro client commands
Notes:
* was only tested with an AWS GA instance
* a similar "curl -x {same-proxy-URI} {website}" works as expected.
* a similar "wget" with $ENV{https_proxy} set also times out.
* pro-client team has an example proxy URI with credentials that exhibits this behavior, but I'll try to come up with another reproducer for that end as well.
Versions: advantage- tools 27.12~22.04.1
ubuntu 22.04.1 LTS
ubuntu-
Thanks,
Dave
Canonical Support