Problem
Hello,
Amazon Q VSCode extension started to have issues with connectivity to Codewhipser endpoints using "https" scheme. Chat window enters infinite loop.
VSCode supports only "http.proxy" variable, however it doesn't get used by some of the extensions that rely on "https" connection scheme.
The issues wasn't experienced in previous versions of the extension.
Steps to reproduce the issue
Use case:
Extension Amazon Q tries to connect to remote HTTPS endpoint such as "codewhisper".
Not working:
- VSCode has "override" proxy support setting
- VSCode has "http.proxy" variable defined
- System doesn't have "http.proxy" or "https.proxy" environment variables
- Outcome: Extension cannot connect to remote host using "https" scheme.
Error: "Error fetching profiles from us-east-1: UnknownEndpoint: Inaccessible host: codewhisperer.us-east-1.amazonaws.com' at port 443'. This service may not be available in the `us-east-1' region.
2025-05-07 13:33:14.121 [info] [2025-05-07T17:33:14.118Z] Amazon Q Token Service Manager: Error updating profiles: Error: Failed to retrieve profiles from all queried regions".
Working:
- VSCode has "override" proxy support setting
- VSCode has "http.proxy" variable defined
- System does define "http.proxy" or "https.proxy" environment variables. VSCode is started from terminal having these properties as part of environment.
- Outcome: Extension successfully connects to remote host using "https" scheme and chat functions properly.
Expected behavior
Amazon Q extension must respect the "http.proxy" variable defined by VSCode IDE even though no other proxy environment variables exist.
System details (run AWS: About and/or Amazon Q: About)
- OS: MacOS
- Visual Studio Code version: 1.99.3
- AWS Toolkit version: N/A
- Amazon Q version: 1.65.0