You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Got into the situation having an HTTP Proxy with Authentication. The environment variable http_proxy was set correctly, but Bundler failed on installing with the source 'https://rubygems.org' with a Network error when fetching a gem and an HTTP Proxy Auth Error on 'http://rubygems.org'. Though I was able to install one gem per bundle install with the http-source before getting the error.
The error is reproducible and has to do with the HTTP Proxy username. In my case it contained an escaped @ character, a %40. When having that in the HTTP Proxy setting, Bundler will first use the correct setting and later (somehow) switch to the unescaped @-version.
This is caused by not escaping HTTP Proxy usernames and passwords in the vendored net/http/persistent library. It's fixed in the original code, so we need to vendor the new version.
Got into the situation having an HTTP Proxy with Authentication. The environment variable
http_proxy
was set correctly, but Bundler failed on installing with the source'https://rubygems.org'
with a Network error when fetching a gem and an HTTP Proxy Auth Error on'http://rubygems.org'
. Though I was able to install one gem perbundle install
with the http-source before getting the error.The error is reproducible and has to do with the HTTP Proxy username. In my case it contained an escaped
@
character, a%40
. When having that in the HTTP Proxy setting, Bundler will first use the correct setting and later (somehow) switch to the unescaped@
-version.Here's a gist to reproduce the error: https://gist.github.com/tbuehlmann/8023219
The text was updated successfully, but these errors were encountered: