Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension ignores http proxy #43

Open
mapero opened this issue Sep 11, 2020 · 3 comments
Open

Extension ignores http proxy #43

mapero opened this issue Sep 11, 2020 · 3 comments
Labels
t/bug Something isn't working

Comments

@mapero
Copy link

mapero commented Sep 11, 2020

Describe the bug
it seems like the visual studio code extension does not use the configured http proxy (http_proxy, https_proxy) in vscode. I am not able to load spectral “extends” from http / https behind corporate proxy. I am unsure to report this as a bug, since I do not have comprehensive logs whats happening, and why it fails.

It seems like spectral is using “PROXY” instead of the linux standard “http_proxy” / “https_proxy”.

Expected behavior
Use vscode proxy settings or linux default http_proxy / https_proxy

Environment:

  • Operating System: Linux

Additional context
Http proxy to comnect to internet

@mapero mapero added the t/bug Something isn't working label Sep 11, 2020
@mapero mapero changed the title Http proxy comfiguration Extension ignores http proxy Sep 11, 2020
@philsturgeon
Copy link
Contributor

philsturgeon commented Feb 1, 2021

@mapero Some work was done to make Spectral support HTTP Proxies via the JS API, I'm wondering if this has helped your situation? It might not be enough, we might need to get some values passed through VS Code and into the JS API, but I was hoping you could help us out and take a look at this one? stoplightio/spectral#1081

@DawMatt
Copy link

DawMatt commented Feb 27, 2024

@philsturgeon , @mapero , this issue still occurs.

The changes made to Spectral to support proxies work when I run Spectral at the command line, including when I run it using the terminal within VS Code itself. The same configuration does not work with the VS Code extension.

@adosaiguas
Copy link

I can confirm this is still an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants