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.

Sign up for GitHub

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

Jump to bottom

Test that Hypercane works effectively with the proxy servers specified in HTTP*_PROXY environment variables #16

Closed
shawnmjones opened this issue Jun 25, 2020 · 2 comments
Closed

Test that Hypercane works effectively with the proxy servers specified in HTTP*_PROXY environment variables #16

shawnmjones opened this issue Jun 25, 2020 · 2 comments
Assignees
@shawnmjones

Comments

@shawnmjones
Copy link
Member

Most *nix commands honor the HTTP_PROXY and HTTPS_PROXY environment variables. Hypercane processes these variables and applies them in hypercane/utils.py as part of get_web_session. We need to test this with Squid or Varnish to ensure the system will actually use a proxy server as a datastore.
@shawnmjones shawnmjones self-assigned this Jun 25, 2020
@shawnmjones
Copy link
Member Author

We use the proxy as a storage cache for content. Many proxies just provide a pass-thru for HTTPS traffic and do not cache it. This is not sufficient for our purposes. We truly need to save mementos so we can process them multiple times, hence our existing MongoDB dependency. Merely supporting these environment variables is insufficient for Hypercane's needs.

@shawnmjones
Copy link
Member Author

This no longer makes sense when considering #65.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shawnmjones shawnmjones

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shawnmjones