To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.
Please avoid AI slops, be concise, and focus on what matters for this issue.
Describe the bug
The server does load the http_proxy variable, but does not load no_proxy, hence the connection to internal gateway API are not possible.
To Reproduce
Steps to reproduce the behavior:
- Start ECA server with environment variables
https_proxy, http_proxy, no_proxy set system-wide
- Start eca client
- /model
403: blocked by proxy
Expected behavior
Connect to the internal API gateway.
Additional context
Variable which is required in certain condition notably when you are behind a proxy, thus require the http_proxy, but your API gateway is internal (home network for example) and must not go through the proxy.
I can see that there is no code related to the variable no_proxy in https://github.com/editor-code-assistant/eca/blob/master/src/eca/network.clj
To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.
Please avoid AI slops, be concise, and focus on what matters for this issue.
Describe the bug
The server does load the
http_proxyvariable, but does not loadno_proxy, hence the connection to internal gateway API are not possible.To Reproduce
Steps to reproduce the behavior:
https_proxy,http_proxy,no_proxyset system-wide403: blocked by proxyExpected behavior
Connect to the internal API gateway.
Additional context
Variable which is required in certain condition notably when you are behind a proxy, thus require the
http_proxy, but your API gateway is internal (home network for example) and must not go through the proxy.I can see that there is no code related to the variable no_proxy in https://github.com/editor-code-assistant/eca/blob/master/src/eca/network.clj