{"thread":{"id":"45941","subject":"clone vs submodule operation with HTTP cURL","startedAt":"2017-05-11T22:05:07Z","lastAt":"2017-05-16T20:48:44Z","messageCount":4,"participants":["Jean-Francois Bouchard","Ævar Arnfjörð Bjarmason"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"319483","messageId":"CAPYmS36e40gb6_2updPKvzo8EJj7+f5npZy9nPDkz1ou8a80_g@mail.gmail.com","threadId":"45941","inReplyTo":null,"subject":"clone vs submodule operation with HTTP cURL","fromName":"Jean-Francois Bouchard","fromEmail":"jfbouchard@accedian.com","sentAt":"2017-05-11T22:04:58Z","receivedAt":"2017-05-11T22:05:07Z","isPatch":false,"sender":{"key":"jfbouchard@accedian.com","avatar":null},"body":"Hello everyone,\n\nIn our usage of GSSAPI via HTTPS, all our operation with git are very\nwell handle, however, when trying to update a submodule, git seems to\nbe managing cURL differently. cURL drop the ball quickly.\n\nExample (No other setup needed on the client) :\ngit clone HTTPrepo -> GET -> 401 -> GET -> 401 -> GET (this time with\nAuthorization: Negotiate)  -> 200 OK\n\ngit submodule update -> GET -> 401 -> git prompt for username\n\nIs the codepath for clone regarding cURL is different than with submodule ?\n\nUsing : 2.13.0, I have also tried the emptyAuth stuff with no avail.\n\nThanks,\nJF\n\n-- \n\n\nAvis de confidentialité\n\nLes informations contenues dans le présent message et dans toute pièce qui \nlui est jointe sont confidentielles et peuvent être protégées par le secret \nprofessionnel. Ces informations sont à l’usage exclusif de son ou de ses \ndestinataires. Si vous recevez ce message par erreur, veuillez s’il vous \nplait communiquer immédiatement avec l’expéditeur et en détruire tout \nexemplaire. De plus, il vous est strictement interdit de le divulguer, de \nle distribuer ou de le reproduire sans l’autorisation de l’expéditeur. \nMerci.\n\nConfidentiality notice\n\nThis e-mail message and any attachment hereto contain confidential \ninformation which may be privileged and which is intended for the exclusive \nuse of its addressee(s). If you receive this message in error, please \ninform sender immediately and destroy any copy thereof. Furthermore, any \ndisclosure, distribution or copying of this message and/or any attachment \nhereto without the consent of the sender is strictly prohibited. Thank you.\n"},{"id":"319838","messageId":"CAPYmS37KTeQDM+iugnEpcxFdPdBxEg3Khg8woptGPE7K-nyjGw@mail.gmail.com","threadId":"45941","inReplyTo":"CAPYmS36e40gb6_2updPKvzo8EJj7+f5npZy9nPDkz1ou8a80_g@mail.gmail.com","subject":"Re: clone vs submodule operation with HTTP cURL","fromName":"Jean-Francois Bouchard","fromEmail":"jfbouchard@accedian.com","sentAt":"2017-05-15T21:38:01Z","receivedAt":"2017-05-15T21:38:08Z","isPatch":false,"sender":{"key":"jfbouchard@accedian.com","avatar":null},"body":"Hello,\n\nFollow-up to this post.\n\nI seems that setting GIT_HTTP_PROXY_AUTHMETHOD=anyauth is a workaround\nto this issue.\n\nSo now the issue is : git is not setting AUTHMETHOD correctly when\ndoing a submodule update\n\nNote that a user is needed in the URL string. :@ does not work,\nempty.auth variable does not work.\n\nAny ideas ?\n\nThanks,\nJF\n\nOn Thu, May 11, 2017 at 6:04 PM, Jean-Francois Bouchard\n<jfbouchard@accedian.com> wrote:\n> Hello everyone,\n>\n> In our usage of GSSAPI via HTTPS, all our operation with git are very\n> well handle, however, when trying to update a submodule, git seems to\n> be managing cURL differently. cURL drop the ball quickly.\n>\n> Example (No other setup needed on the client) :\n> git clone HTTPrepo -> GET -> 401 -> GET -> 401 -> GET (this time with\n> Authorization: Negotiate)  -> 200 OK\n>\n> git submodule update -> GET -> 401 -> git prompt for username\n>\n> Is the codepath for clone regarding cURL is different than with submodule ?\n>\n> Using : 2.13.0, I have also tried the emptyAuth stuff with no avail.\n>\n> Thanks,\n> JF\n\n-- \n\n\nAvis de confidentialité\n\nLes informations contenues dans le présent message et dans toute pièce qui \nlui est jointe sont confidentielles et peuvent être protégées par le secret \nprofessionnel. Ces informations sont à l’usage exclusif de son ou de ses \ndestinataires. Si vous recevez ce message par erreur, veuillez s’il vous \nplait communiquer immédiatement avec l’expéditeur et en détruire tout \nexemplaire. De plus, il vous est strictement interdit de le divulguer, de \nle distribuer ou de le reproduire sans l’autorisation de l’expéditeur. \nMerci.\n\nConfidentiality notice\n\nThis e-mail message and any attachment hereto contain confidential \ninformation which may be privileged and which is intended for the exclusive \nuse of its addressee(s). If you receive this message in error, please \ninform sender immediately and destroy any copy thereof. Furthermore, any \ndisclosure, distribution or copying of this message and/or any attachment \nhereto without the consent of the sender is strictly prohibited. Thank you.\n"},{"id":"319948","messageId":"CAPYmS35nxV2mgvhwOxwh_0bjbR6PrjEPmLbAZd0kDFN_rpccsw@mail.gmail.com","threadId":"45941","inReplyTo":"CAPYmS37KTeQDM+iugnEpcxFdPdBxEg3Khg8woptGPE7K-nyjGw@mail.gmail.com","subject":"Re: clone vs submodule operation with HTTP cURL","fromName":"Jean-Francois Bouchard","fromEmail":"jfbouchard@accedian.com","sentAt":"2017-05-16T18:15:39Z","receivedAt":"2017-05-16T18:15:45Z","isPatch":false,"sender":{"key":"jfbouchard@accedian.com","avatar":null},"body":"Hello,\n\nAnyone can help with this ? The workaround is hardly possible in a\nmedium environment as it needs editing and adding env to everyone and\nin every clone.\n\nThanks !!\nJF\n\nOn Mon, May 15, 2017 at 5:38 PM, Jean-Francois Bouchard\n<jfbouchard@accedian.com> wrote:\n> Hello,\n>\n> Follow-up to this post.\n>\n> I seems that setting GIT_HTTP_PROXY_AUTHMETHOD=anyauth is a workaround\n> to this issue.\n>\n> So now the issue is : git is not setting AUTHMETHOD correctly when\n> doing a submodule update\n>\n> Note that a user is needed in the URL string. :@ does not work,\n> empty.auth variable does not work.\n>\n> Any ideas ?\n>\n> Thanks,\n> JF\n>\n> On Thu, May 11, 2017 at 6:04 PM, Jean-Francois Bouchard\n> <jfbouchard@accedian.com> wrote:\n>> Hello everyone,\n>>\n>> In our usage of GSSAPI via HTTPS, all our operation with git are very\n>> well handle, however, when trying to update a submodule, git seems to\n>> be managing cURL differently. cURL drop the ball quickly.\n>>\n>> Example (No other setup needed on the client) :\n>> git clone HTTPrepo -> GET -> 401 -> GET -> 401 -> GET (this time with\n>> Authorization: Negotiate)  -> 200 OK\n>>\n>> git submodule update -> GET -> 401 -> git prompt for username\n>>\n>> Is the codepath for clone regarding cURL is different than with submodule ?\n>>\n>> Using : 2.13.0, I have also tried the emptyAuth stuff with no avail.\n>>\n>> Thanks,\n>> JF\n\n-- \n\n\nAvis de confidentialité\n\nLes informations contenues dans le présent message et dans toute pièce qui \nlui est jointe sont confidentielles et peuvent être protégées par le secret \nprofessionnel. Ces informations sont à l’usage exclusif de son ou de ses \ndestinataires. Si vous recevez ce message par erreur, veuillez s’il vous \nplait communiquer immédiatement avec l’expéditeur et en détruire tout \nexemplaire. De plus, il vous est strictement interdit de le divulguer, de \nle distribuer ou de le reproduire sans l’autorisation de l’expéditeur. \nMerci.\n\nConfidentiality notice\n\nThis e-mail message and any attachment hereto contain confidential \ninformation which may be privileged and which is intended for the exclusive \nuse of its addressee(s). If you receive this message in error, please \ninform sender immediately and destroy any copy thereof. Furthermore, any \ndisclosure, distribution or copying of this message and/or any attachment \nhereto without the consent of the sender is strictly prohibited. Thank you.\n"},{"id":"319964","messageId":"CACBZZX7ZNUUVWC2dWij-U=UAGgbuvVbhSQhVggtSWHcL8D+K5g@mail.gmail.com","threadId":"45941","inReplyTo":"CAPYmS35nxV2mgvhwOxwh_0bjbR6PrjEPmLbAZd0kDFN_rpccsw@mail.gmail.com","subject":"Re: clone vs submodule operation with HTTP cURL","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2017-05-16T20:48:08Z","receivedAt":"2017-05-16T20:48:44Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Tue, May 16, 2017 at 8:15 PM, Jean-Francois Bouchard\n<jfbouchard@accedian.com> wrote:\n> Hello,\n>\n> Anyone can help with this ? The workaround is hardly possible in a\n> medium environment as it needs editing and adding env to everyone and\n> in every clone.\n\nAccording to git-config anyauth is the default, see http.proxyAuthMethod.\n\nDo you have something setting http.proxyAuthMethod in the environment\nbeforehand? What does:\n\n    git config http.proxyAuthMethod\n\nReturn, in the same environment where your cloning fails? Same for\nGIT_HTTP_PROXY_AUTHMETHOD.\n\n\n\n> Thanks !!\n> JF\n>\n> On Mon, May 15, 2017 at 5:38 PM, Jean-Francois Bouchard\n> <jfbouchard@accedian.com> wrote:\n>> Hello,\n>>\n>> Follow-up to this post.\n>>\n>> I seems that setting GIT_HTTP_PROXY_AUTHMETHOD=anyauth is a workaround\n>> to this issue.\n>>\n>> So now the issue is : git is not setting AUTHMETHOD correctly when\n>> doing a submodule update\n>>\n>> Note that a user is needed in the URL string. :@ does not work,\n>> empty.auth variable does not work.\n>>\n>> Any ideas ?\n>>\n>> Thanks,\n>> JF\n>>\n>> On Thu, May 11, 2017 at 6:04 PM, Jean-Francois Bouchard\n>> <jfbouchard@accedian.com> wrote:\n>>> Hello everyone,\n>>>\n>>> In our usage of GSSAPI via HTTPS, all our operation with git are very\n>>> well handle, however, when trying to update a submodule, git seems to\n>>> be managing cURL differently. cURL drop the ball quickly.\n>>>\n>>> Example (No other setup needed on the client) :\n>>> git clone HTTPrepo -> GET -> 401 -> GET -> 401 -> GET (this time with\n>>> Authorization: Negotiate)  -> 200 OK\n>>>\n>>> git submodule update -> GET -> 401 -> git prompt for username\n>>>\n>>> Is the codepath for clone regarding cURL is different than with submodule ?\n>>>\n>>> Using : 2.13.0, I have also tried the emptyAuth stuff with no avail.\n>>>\n>>> Thanks,\n>>> JF\n>\n> --\n>\n>\n> Avis de confidentialité\n>\n> Les informations contenues dans le présent message et dans toute pièce qui\n> lui est jointe sont confidentielles et peuvent être protégées par le secret\n> professionnel. Ces informations sont à l’usage exclusif de son ou de ses\n> destinataires. Si vous recevez ce message par erreur, veuillez s’il vous\n> plait communiquer immédiatement avec l’expéditeur et en détruire tout\n> exemplaire. De plus, il vous est strictement interdit de le divulguer, de\n> le distribuer ou de le reproduire sans l’autorisation de l’expéditeur.\n> Merci.\n>\n> Confidentiality notice\n>\n> This e-mail message and any attachment hereto contain confidential\n> information which may be privileged and which is intended for the exclusive\n> use of its addressee(s). If you receive this message in error, please\n> inform sender immediately and destroy any copy thereof. Furthermore, any\n> disclosure, distribution or copying of this message and/or any attachment\n> hereto without the consent of the sender is strictly prohibited. Thank you.\n"}]}