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
People behind proxies simply set the environment variables so that bower sees the proxy. While this works for normal requests, it is not enough for git://. Users have also to configure git to use https.insteadOf.git.
We can do this for github endpoints since they support https. For others we can't do this since https is not supported but we can error out with an appropriate message telling the possible cause for the issue and how to solve it.
Went ahead and put together a fix for this. Put in the change early enough in the resolver lifecycle as to not mess with what is going on inside. Check it out.
People behind proxies simply set the environment variables so that bower sees the proxy. While this works for normal requests, it is not enough for
git://
. Users have also to configuregit
to usehttps.insteadOf.git
.We can do this for github endpoints since they support
https
. For others we can't do this sincehttps
is not supported but we can error out with an appropriate message telling the possible cause for the issue and how to solve it.http://stackoverflow.com/questions/15669091/bower-install-using-only-https
The text was updated successfully, but these errors were encountered: