The formatter doesn't seem to use the VSCode proxy for downloading xsd files

[halloleo]

When the extension formats a pom.xml (which contains an XML Schema) VS Code issues the problem "Error while downloading 'http://maven.apache.org/xsd/maven-4.0.0.xsd'...".

I have defined a proxy in VS Code's settings, but I assume the extension does not obey/use this proxy.

Is there another way to tell the formatter to use a proxy?

[fbricon]

Please see if https://github.com/redhat-developer/vscode-xml/blob/master/docs/Proxy.md helps

[halloleo]

Thanks @fbricon !

I have set http.proxy in vscode's settings. I don't need authorisation.

I left http.proxySupport alone, showing "override" in the dialog.

This is from my understanding exactly what the page you link to says - but it doesn't work.

PS: On the page is the strange sentence: "If you set [http.proxySupport] to override, VS Code will attempt to rewrite the requests from extensions to go through the proxy that is configured for VS Code. However, this method sometimes does not work correctly." - In my case it doesn't seem to work correctly indeed, so what can I do?

[fbricon]

@datho7561 can you please investigate?

[datho7561]

Hello! I've tried on my machine with this proxy, and everything appears to be working.

Which version of the extension are you using? Which version of VS Code (/Codium/Theia/?) are you using?

One thing that might be related is that http://maven.apache.org/xsd/maven-4.0.0.xsd redirects to the https version of the website; maybe something goes wrong when trying to handle this redirect? I'll research some more.

[halloleo]

Thanks for chiming in, @datho7561!

I use VS Code from the Microsoft RPM. The machine is a RHEL 8 Linux box on a corporate network.

The proxy software is px-proxy on a RHEL 7 box. The redirect might be the problem for the proxy. I'll test this outside VS Code soon.

[halloleo]

Just FYI: When I do

wget http://maven.apache.org/xsd/maven-4.0.0.xsd

with the px-proxy entered in my .wgetrc, hen I can download the schema without problems.

[datho7561]

Okay. I'll investigate some more today. Likely my proxy setup was allowing traffic to bypass the proxy

[datho7561]

I was able to get a proper setup where my machine needs to use the proxy to access the http/https, and I am able to reproduce the issue.

[datho7561]

I figured out the issue and am working on the PR. In the mean time, here is a workaround: https://github.com/redhat-developer/vscode-xml/blob/master/docs/Preferences.md#server-vm-arguments. My PR will just make sure that these parameters are set for you if you have set http.proxy in the VS Code settings.

[halloleo]

Thanks that you looked into this! :)

[angelozerr]

@datho7561 @halloleo is it this issue fixed?

[datho7561]

@angelozerr It should be fixed in the prereleases, but we haven't released since then

[angelozerr]

@datho7561 I think we can close this issue no?