[Codespaces VS Code Extension] HTTP 400 (Bad Request) when connect to Codespace behind Proxy #129850
Unanswered
clemensfreitagbosch
asked this question in
Codespaces
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Bug
Body
Background
We are using Codespaces in a corporate environment. Regular Clients need to use a HTTP Proxy to access Internet Services.
The correct Proxy settings are configured in the Browser and the
http_proxy
/https_proxy
environment variables.VS Code Version: 1.90.2 (Windows)
Codespaces Extension Version: 1.16.23
Issue
I have no issues to use Codespaces within the Browser, but when using VS Code Desktop I run into a HTTP 400 (Bad Request) when trying while trying to reach
euw.rel.tunnels.api.virtualstudio.com
Analysis
I did some research by inspecting the network traffic with Wireshark. When using Codespace in the Browser, one can observe a successful HTTP
CONNECT
request toeuw-data.rel.tunnels.api.virtualstudio.com
with a HTTP 200 Response from the Proxy.However, when using VS Code Desktop there is a HTTP GET request towards the proxy
euw.rel.tunnels.api.virtualstudio.com
with a 400 Bad Request from the Proxy:
--> I would not expect a GET request here, rather a CONNECT as seen in the Browser. A direct GET towards the Proxy does not makes sense.
A simple
curl -X GET euw.rel.tunnels.api.virtualstudio.com
from the same machine is successful (cURL will be aware of thehttps_proxy
environmental variable and will send CONNECT requests to the Proxy automatically).Beta Was this translation helpful? Give feedback.
All reactions