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

Proxy configuration #166

Open
ricovitch opened this issue Jul 8, 2021 · 8 comments
Open

Proxy configuration #166

ricovitch opened this issue Jul 8, 2021 · 8 comments

Comments

@ricovitch
Copy link

Hi,

I'd like to use this tool behind a corporate proxy, and I don't get how to configure the proxy, if possible.
I checked internal through link-check and needle.

I thought from reading at this issue that would be possible tcort/link-check#29

Looking at needle documentation we would have to pass a proxy or agent option for that : https://github.com/tomas/needle#request-options

Currently there does not seem to be an option in order to configure a proxy, or am I missing something ?

@btel
Copy link

btel commented Oct 8, 2021

same here, it seems not to work behind proxy even with http(s)_proxy variables defined

@nejch
Copy link

nejch commented Jan 24, 2022

Hi @tcort, I tried to move this topic upstream for full support in needle itself e.g. including no_proxy, in tomas/needle#382, as using the standard environment variables is usually the way to go. But that doesn't seem to be picking up - would you still be interested in doing this on the link-check side? It does seem like the older request library already had full support for this https://github.com/request/request/blob/3c0cddc7c8eb60b470e9519da85896ed7ee0081e/README.md?plain=1#L568-L578

@fhaftmann
Copy link

The PR against needle seems to be merged in upstream release 3.1.0 (tomas/needle@8353cdb).

A corresponding dependency bump would be needed to turn it effective for markdown-link-check.

@nejch
Copy link

nejch commented Apr 26, 2022

@fhaftmann you can already bump needle yourself as markdown-link-check does not pin it to the exact version:
https://github.com/tcort/markdown-link-check/blob/master/package.json#L42

However, the implementation of no_proxy in that PR only seems to cover exact hosts, but not domains or ports (see discussion in tomas/needle#383), so not sure that'll fix the issue for you entirely.

@axel3rd
Copy link

axel3rd commented Sep 23, 2022

However, the implementation of no_proxy in that PR only seems to cover exact hosts, but not domains or ports (see discussion in tomas/needle#383), so not sure that'll fix the issue for you entirely.

Confirmed => only way to support http_proxy / https_proxy / no_proxy is to use/downgrade markdown-link-check to
3.8.7 😢

@dklimpel
Copy link
Contributor

I can also confirm. No matter how I set https_proxy I get only errors 502 and 503 for external URLs. With 3.8.7 there are no problems. Verbose output -v does not show more information.

@dklimpel
Copy link
Contributor

IMO the problem is an upstream bug: tomas/needle#406

@dklimpel
Copy link
Contributor

This was fixed for me at v3.12.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants