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

Per link (download) proxy config #3899

Open
z3ch5 opened this issue Feb 14, 2021 · 2 comments · May be fixed by #4486
Open

Per link (download) proxy config #3899

z3ch5 opened this issue Feb 14, 2021 · 2 comments · May be fixed by #4486
Assignees
Labels
feature request New enhancement request pyLoad Next

Comments

@z3ch5
Copy link

z3ch5 commented Feb 14, 2021

I am not sure how easy is to implement such a feature, but for sure it is a great one, I think it is necessary to make the download (any link) has specific configuration for proxy, and weither to use it or not, and maybe adding multiple proxies (profiling proxies to choose from list) ??

the current situation which is a proxy for pyload in general doesn't suit my need, as some services blocks VPNs and I need to use for example TOR for some links, and for others no proxy.

@Kapujino
Copy link

I found #4294 and #4295 basically request the same feature.
It would be great to balance the downloads randomly over a list of (socks5) proxies or to be able to do this with a PAC file.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file

Pyload has a lot of great features while it's lightweight with a local webgui. The proxy list feature is the only thing holding me back migrating to pyload.

@milahu
Copy link

milahu commented Jun 14, 2024

draft in #4478
currently this fails because no chunks are downloaded

tor works

curl --proxy socks5h://[email protected]:9050 https://httpbin.org/ip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New enhancement request pyLoad Next
Development

Successfully merging a pull request may close this issue.

4 participants