The proxy server in vscode settings, blocks access to tabby on localhost

[n-r-w]

If proxy is enabled in vs code (http.proxy option), and tabby is installed locally, then it is impossible to connect to it.

vscode config:

    "http.proxyStrictSSL": false,
    "http.proxyAuthorization": null,
    "http.proxySupport": "on",
    "http.proxy": "http://10.222.3.4:2080",

tabby started:

Version 0.19.0
🚀 Listening at http://0.0.0.0:8080

tabby logs:

024-11-02 00:22:01.498 [info] [Info  - 12:22:01 AM] [Proxy] Using proxy http://10.222.3.4:2080.
2024-11-02 00:22:01.519 [info] [Debug - 12:22:01 AM] [TabbyApiClient] Health check request: GET http://127.0.0.1:8080/v1/health. [de789c23-695c-45d1-8851-600cb4450146]
2024-11-02 00:22:01.520 [info] [Debug - 12:22:01 AM] [TabbyLSP] Internal components initialized.
2024-11-02 00:22:01.521 [info] [Debug - 12:22:01 AM] [TabbyLSP] Initializing feature components...
2024-11-02 00:22:01.521 [info] [Info  - 12:22:01 AM] [RecentlyChangedCodeSearch] Created code search engine for recently changed files.
2024-11-02 00:22:01.522 [info] [Debug - 12:22:01 AM] [TabbyLSP] Feature components initialized.
2024-11-02 00:22:01.524 [info] [Info  - 12:22:01 AM] [TabbyLSP] Initialize done.
2024-11-02 00:22:01.528 [info] [Tabby] Tabby extension activated.
2024-11-02 00:22:01.528 [info] [Error - 12:22:01 AM] [TabbyApiClient] Health check request failed. [de789c23-695c-45d1-8851-600cb4450146] {
  "error": {}
}

[zwpaper]

hi @n-r-w, thanks for trying Tabby,

After you set the proxy, all network connections go through the proxy even localhost, so you might need to add a noproxy setting to bypass the proxy for localhost.

I also found vscode has mark this proxy settings legacy, you can check more on https://code.visualstudio.com/docs/setup/network

[n-r-w]

hi @n-r-w, thanks for trying Tabby,

After you set the proxy, all network connections go through the proxy even localhost, so you might need to add a noproxy setting to bypass the proxy for localhost.

I also found vscode has mark this proxy settings legacy, you can check more on https://code.visualstudio.com/docs/setup/network

On the one hand, it sounds logical. But on the other hand, tabby uses this "outdated" http.proxy parameter, but ignores http.NoProxy settings.

[n-r-w]

It seems that in this merge request they forgot about http.NoProxy https://github.com/TabbyML/tabby/pull/2921/files