Cannot attach to debugger

[gielfeldt]

Hope this is the right place/project, otherwise my apologies.

When debugging nodejs using attach, vscode connects to the nodejs debugger using the address specified in launch.json

However, it seems to always use "localhost" in the host header for the requests it make.

This prevents me from routing the traffic through a proxy which needs host names in order to route properly

Is there anyway to control the host header in vscode's requests to the nodejs debugger?

Thanks

A sniffed snippet example from request vscode => nodejs debugger:

GET /json/version HTTP/1.1
user-agent: got (https://github.com/sindresorhus/got)
accept: application/json
host: localhost
accept-encoding: gzip, deflate, br
Connection: close

Another snippet from the ws upgrade request:

GET /6cabf470-7eb5-4202-b11f-4355c178c8a3 HTTP/1.1
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: qDfnpxTOzSjxQfbiJcsTWQ==
Connection: Upgrade
Upgrade: websocket
host: localhost

[connor4312]

However, it seems to always use "localhost" in the host header for the requests it make.

This is required; if the host isn't set to localhost then the debug target (node or chrome) will refuse to respond with debug information.

If the host header is not localhost, you will need to fix it up in your proxy. I would be willing to accept a PR to configure a custom value for the host header.

[gielfeldt]

Thanks for the quick reply. I'll see what I can do and create a PR for it.

[connor4312]

Code pointers:

Used

vscode-js-debug/src/targets/browser/spawn/endpoints.ts

Line 17 in 7a446b4

export async function getWSEndpoint(

and

vscode-js-debug/src/cdp/webSocketTransport.ts

Line 32 in 7a446b4

headers: { host: 'localhost' },

Interface for the launch configuration:

vscode-js-debug/src/configuration.ts

Line 87 in 7a446b4

export interface IBaseConfiguration extends IMandatedConfiguration {

[Kingwl]

Hi folks.

I have sent a PR to fix this one because i saw there's no activities for 1 year.

[connor4312]

Thank you for the PR. However, in the intervening time period, there has been no further requests for this feature. Considering that, at least in the case of OP, there was a simple workaround for him, I'm not sure I want to take this on.

Do you have a use case for this, Wenlu Wang (@Kingwl), and can you describe it?

[Kingwl]

Sure.
I'm going to debugger a node instance remotely.
And we have a gateway to detect invalid request. It's will deny the request who send by the debugger which has the host: localhost header.

[chiefbrain]

With this PR, I could route debug connections to the correct container based on the subdomain using the following nginx-config.

server {
  listen 9229;
  server_name         ~^(?<sub>.*).domain.tld$;

  location / {
    resolver 127.0.0.11;
    proxy_set_header Host $host;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_pass http://$sub:9229;
  }
}