Re: [PATCH] http: add http.version option to select http protocol version
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Dec 11, 2018, 12:40 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1812111334260.43@tvgsbejvaqbjf.bet>
- In-Reply-To
- <CAPig+cQW5_9fH-P8X50Mx5kGJRwEOskw2L49Ajk+3D4xWpcOHg@mail.gmail.com>
Hi Eric,
On Mon, 10 Dec 2018, Eric Sunshine wrote:
Show 8 quoted lines
> On Mon, Dec 10, 2018 at 5:50 PM Silvio Fricke <silvio.fricke@gmail.com> wrote: > > HTTP has several protocol versions. By default, libcurl is using HTTP/2 > > today and check if the remote can use this protocol variant and fall > > back to a previous version if not. > > > > Under rare conditions it is needed to switch the used protocol version > > to fight again wrongly implemented authorization mechanism like ntlm > > with gssapi on remote side.
Please note that this has been addressed for NTLM in https://github.com/curl/curl/pull/3345 and the gssapi problem is probably worked around by https://github.com/curl/curl/pull/3349.
Both patches were backported to the cURL version included in Git for Windows v2.20.0.
> > Signed-off-by: Silvio Fricke <silvio.fricke@gmail.com> > > This looks very similar to [1] which is already in Junio's "next" > branch (although not yet in a released version of Git).
Small correction: it is in Git *for Windows* v2.20.0, so in a manner of speaking it *is* in a released version of Git.
The reason: even if we included the NTLM/Kerberos patches in Git for Windows, there might be other scenarios where neither of those patches catch.
Ciao, Johannes
> [1]: https://public-inbox.org/git/71f8b71b346f132d0dc9a23c9a7f2ca2cb91966f.1541735051.git.gitgitgadget@gmail.com/ >