Closed hariharshankar closed 4 years ago
additional note: The request module should take care of the environment variables. But somehow it doesn't within the client. Setting a proxy option here will succeed. But setting a proxy option in a config.json will not.
Tried this:
config.json:
{
"proxy": "http://my.proxy.com:1234"
}
and
ldf-client http://fragments.dbpedia.org/2014/en -f q.sparql -c config.json
There is currently no support for HTTP proxies, but we can add this as a feature.
@cKlee We have stopped using request
because it led to socket problems.
I would (still) appreciate if you add this feature. I have no idea where to put a proxy setting. Otherwise I would make a PR, but I can't.
@cKlee Would proxychains
help you in the meantime?
Thank you Ruben for the hint. Proxychains4 works for me. Nevertheless a proxy-option would be nice.
This project has now been deprecated in favor of Comunica, where this feature is supported.
Is there a way to tell the client to use an HTTP proxy?
By default, it does not recognize either the system wide HTTP proxy settings, or the proxy set using the environment variables http_proxy, https_proxy.