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
Support a proxy mode for outbound HTTP and HTTPS traffic #83
Comments
havard#83 Conflicts: openid.js
I have been gathering opinions on the matter through the nodejs mailing list and discussions with various developers. The environment variable proposal seems to be a good solution. One suggestion though: How about splitting |
Thanks for looking into this and coordinating with the broader community. It would be good to use the same solution across this and node-oauth. I'm fine with These env variables. I'll update my fork once I'm back from traveling. I've also found separating HTTP and HTTPS settings useful. |
Merged and fixed in ead2635 |
This is great, thanks again! Any timelines for a 0.4.3 release? |
I am gonna let it sit for a few days and see if anyone reports problems, then make a release. |
Please consider adding support for a HTTP proxy everywhere node-openid uses the http or https node module.
Suggested API:
node-openid would look for an environment variable HTTP_PROXY and if present, respect it.
Example:
Use Cases:
Security and Performance
When we deploy services, we put them behind squid or another proxy layer. This allows us to deny outbound http requests to unknown urls. It allows us to locally cache OpenID responses (for the calls that are cachable).
Load Testing
We're looking at also using this setting for load testing, so we don't hit 3rd party OpenID endpoints.
The text was updated successfully, but these errors were encountered: