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
(How) is no_proxy supported? #700
Comments
Hi @JasonBarnabe, I'm sorry about the confusion. If you check when that method is actually called, you'll see that function can only be reached if So release notes don't go too much into details but simply say things as they are: we support the no_proxy automatically, but only starting from Ruby 2.0 😄 |
OK, thanks for the info. I did see |
Oh I see. Simply the method |
Using faraday 0.12.2, I am getting this output on Ruby 2.3.3 & 2.4.2 currently. Is this a regression? When running my build on CircleCI's 2.3.3, or 2.4.2 docker image, I see this:
UPDATE: Seems I am experiencing #701 which has been fixed, and there is a new release of faraday. Until @intridea loosens the faraday version constraint in oauth2 (please thumb!) we will be forking oauth2, or dealing with old faraday. |
Version 0.12.0 in the release notes says "Proxy feature now relies on Ruby URI::Generic#find_proxy and can use no_proxy ENV variable (not compatible with ruby < 2.0)". Great! However I noticed this line:
So is
no_proxy
supported or not? Or maybe supported sometimes? Please fix or document this.The text was updated successfully, but these errors were encountered: