Skip to content

Conversation

@SwiftExtender
Copy link

Sometimes archive.org cant be accessed without proxy so i added support for proxy specifying
CLI Example:
waybackpack url --proxy http://host:port -d output_folder

Also i added support for dont verifiying certs. It can be helpful is CA of archive.org cant be trusted (in rare cases it can be fired by using proxies)
CLI Example:
waybackpack url --proxy http://host:port --no-verify-certificate -d output_folder

@jsvine
Copy link
Owner

jsvine commented Apr 21, 2025

Since waybackpack relies on the requests module for fetching archived pages, I believe setting the HTTP{S}_PROXY environment variables should work here, without any need for modifying the code:

Screenshot 2025-04-20 at 10 39 18 PM

... but does that not work for your use case? If so, could you include a test that helps verify/debug?

@SwiftExtender
Copy link
Author

Setting PROXY env variables override proxy settings for programs written on Python, Ruby, Go. I would like to set different proxies for different processes

@jsvine
Copy link
Owner

jsvine commented Apr 24, 2025

If I'm understanding your concern correctly, you can also set environment variables on a process-level, e.g.:

HTTPS_PROXY="https://example.com" waybackpack [...]

... which would set the environment variable just for that invocation and not affect any other processes.

@SwiftExtender
Copy link
Author

Ok, option for setting proxy may be not useful, but setting disable of certificate check still important

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

Successfully merging this pull request may close these issues.

2 participants