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: Wed, 5 Jun 2013 08:58:07 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1306050851210.4783@tvnag.unkk.fr> (raw)
In-Reply-To: <630928524B6441DC907D7AFF34389010@gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 816 bytes --]

On Tue, 4 Jun 2013, Janusz Harkot wrote:

> valid point, but from what you can find on the web, the only solution 
> provided everywhere was to disable certificate checking… so maybe that's not 
> me, but this is first time someone spent some time to check whats going on 
> :)

I don't disagree with that. You may be right.

But I am the maintainer of libcurl and I have *never* gotten a report about 
this before, and I rather base my actions and assumptions on true reports from 
actual developers with whom I can discuss and delve into details with (like 
you and me right now). Basing decisions on vague statements posted elsewhere 
by unknown people is for sure a road into sadness.

Anyway, now I'm off topic. I'm glad you could fix the problem. Thanks for 
flying git + libcurl! =)

-- 

  / daniel.haxx.se

      reply	other threads:[~2013-06-05  6:58 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
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 [this message]

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.1306050851210.4783@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).