Re: clone vs submodule operation with HTTP cURL

On Tue, May 16, 2017 at 8:15 PM, Jean-Francois Bouchard wrote: > Hello, > > Anyone can help with this ? The workaround is hardly possible in a > medium environment as it needs editing and adding env to everyone and > in every clone. According to git-config anyauth is the

Re: clone vs submodule operation with HTTP cURL

Hello, Anyone can help with this ? The workaround is hardly possible in a medium environment as it needs editing and adding env to everyone and in every clone. Thanks !! JF On Mon, May 15, 2017 at 5:38 PM, Jean-Francois Bouchard wrote: > Hello, > > Follow-up to this

Re: clone vs submodule operation with HTTP cURL

Hello, Follow-up to this post. I seems that setting GIT_HTTP_PROXY_AUTHMETHOD=anyauth is a workaround to this issue. So now the issue is : git is not setting AUTHMETHOD correctly when doing a submodule update Note that a user is needed in the URL string. :@ does not work, empty.auth variable

clone vs submodule operation with HTTP cURL

Hello everyone, In our usage of GSSAPI via HTTPS, all our operation with git are very well handle, however, when trying to update a submodule, git seems to be managing cURL differently. cURL drop the ball quickly. Example (No other setup needed on the client) : git clone HTTPrepo -> GET -> 401