git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Daniel Stenberg <daniel@haxx.se>
To: Janusz Harkot <janusz.harkot@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: SNI (SSL virtual hosts)
Date: Tue, 4 Jun 2013 11:45:26 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1306041142200.16303@tvnag.unkk.fr> (raw)
In-Reply-To: <97F8F367D27D4B3E93439FF8D0F121FA@gmail.com>

On Tue, 4 Jun 2013, Janusz Harkot wrote:

> Strange was, that initial communication was OK (http GET), but when there 
> was http POST - git reported error (incorrect certificate). The only 
> workaround was to disable certificate verification.
>
> My question is: does git support SNI on the https? If so - are there 
> (undocumented) options to make it work?

It does. git uses libcurl for the HTTPS parts and it has support SNI for a 
long time, assuming you built libcurl with a TLS library that handles it.

Which libcurl version and SSL backend is this? (curl -V usually tells)

If you made it working by disabling certificate verification then it sounds as 
if SNI might still have worked and the problem was rahter something else, as 
without SNI you can't do name-based virtual hosting over HTTPS - but perhaps 
you wanted to communicate with the "default" server on that IP?

-- 

  / daniel.haxx.se

  reply	other threads:[~2013-06-04  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DC851F5EA18E478DACB62178624BF5B7@gmail.com>
2013-06-04  9:36 ` SNI (SSL virtual hosts) Janusz Harkot
2013-06-04  9:45   ` Daniel Stenberg [this message]
2013-06-04 10:19     ` Janusz Harkot
2013-06-04 11:58       ` Daniel Stenberg
2013-06-04 16:59         ` Janusz Harkot
2013-06-04 21:18           ` Daniel Stenberg
2013-06-04 21:26             ` Janusz Harkot
2013-06-05  6:58               ` Daniel Stenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.00.1306041142200.16303@tvnag.unkk.fr \
    --to=daniel@haxx.se \
    --cc=git@vger.kernel.org \
    --cc=janusz.harkot@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).