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
It would be great to have support for HTTP/HTTPS proxies for people sitting behind corporate proxies who clone/push/pull to remote repositories. It looks like libgit2 is only supporting this in the winhttp transport backend and that there is an open issue libgit2/libgit2#2555 to support it by default.
As a followup, in the meantime if someone else stumbles upon that problem, using a tool like proxychains-ng https://github.com/rofl0r/proxychains-ng might ease the pain.
Yeah, unfortunately proxy support is only implemented in the curl and openSSL transport streams, neither of which are currently used by NodeGit. @implausible knows a little more, but NodeGit needs to be able to use one of those for us to be able to utilize libgit's proxy support. It also needs to be fixed in NodeGit(the generated code isn't working properly), but that should be much simpler than the curl/openSSL issues.
I've been trying to use this (proxyOpts on push) but don't seem to be doing something correctly. Can someone provide an example of how to use proxy with un/pw in a push? Don't see any tests that show it either.
To be clear, the credentials callback is never invoked.
I'm using 0.19.0. My proxyOpts passed into pushOptions is as follows:
I've been trying to use this (proxyOpts on push) but don't seem to be doing something correctly. Can someone provide an example of how to use proxy with un/pw in a push? Don't see any tests that show it either.
To be clear, the credentials callback is never invoked. I'm using 0.19.0. My proxyOpts passed into pushOptions is as follows:
Activity
johnhaley81 commentedon Mar 16, 2015
When that is closed out on libgit2 and released we'll make sure to get that into NodeGit as well. Thanks!
franckstauffer commentedon Mar 16, 2015
As a followup, in the meantime if someone else stumbles upon that problem, using a tool like proxychains-ng https://github.com/rofl0r/proxychains-ng might ease the pain.
tbranyen commentedon Mar 24, 2015
Closing this as we cannot address it at this time. As @johnhaley81 said, once it lands and is tagged in libgit2 it'll be available here.
franckstauffer commentedon Mar 24, 2015
Ok fair enough...I only created the issue because @johnhaley81 invited me to do so on gitter!
tbranyen commentedon Mar 24, 2015
Sure, don't take it as a jab, I'm just trying to tidy up the issue tracker :)
johnhaley81 commentedon Mar 24, 2015
I just wanted some kind of history :)
maxkorp commentedon Mar 24, 2015
Labeling this, so we can zip through the closed stuff later and see if this has been addressed.
Kerrick commentedon Apr 21, 2016
Looks like libgit2 merged in support for proxies! libgit2/libgit2#3110
johnhaley81 commentedon Apr 21, 2016
Working on merging that now :)
vbarshai commentedon Aug 15, 2016
@johnhaley81 Has this ever been merged? Or is the issue still open? Thanks!
cbargren commentedon Aug 19, 2016
Proxy support did get merged in, this can probably be closed.
vbarshai commentedon Aug 19, 2016
Thanks @cbargren it's been merged in v0.15.0 but looks like the latest builds break:
babel --presets es2015 -d ./dist ./lib (no lib dir)
hellosmithy commentedon Sep 7, 2016
Has anyone managed to get this working behind a corporate proxy?
vbarshai commentedon Sep 7, 2016
@hellosmithy not on our side - ended up having to use proxy exports and native git commands as a workaround until a stable release.
johnhaley81 commentedon Sep 7, 2016
@cbargren and @implausible were working on getting something going here but ran into some bigger issues.
cbargren commentedon Sep 7, 2016
Yeah, unfortunately proxy support is only implemented in the curl and openSSL transport streams, neither of which are currently used by NodeGit. @implausible knows a little more, but NodeGit needs to be able to use one of those for us to be able to utilize libgit's proxy support. It also needs to be fixed in NodeGit(the generated code isn't working properly), but that should be much simpler than the curl/openSSL issues.
johnhaley81 commentedon Feb 6, 2017
This is now fixed on master.
clearly commentedon May 9, 2017
I've been trying to use this (proxyOpts on push) but don't seem to be doing something correctly. Can someone provide an example of how to use proxy with un/pw in a push? Don't see any tests that show it either.
To be clear, the credentials callback is never invoked.
I'm using 0.19.0. My proxyOpts passed into pushOptions is as follows:
kriks7iitk commentedon Jan 29, 2024
D
@clearly is it solved??