From: Daniel Stenberg <daniel@haxx.se>
To: Mika Fischer <mika.a.fischer@googlemail.com>
Cc: kusmabite@gmail.com, msysGit <msysgit@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [msysGit] Git unable to access https repositories due to curl/OpenSSL 1.0.0 handshake issues
Date: Wed, 26 Jan 2011 23:00:39 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.00.1101262244550.14066@tvnag.unkk.fr> (raw)
In-Reply-To: <AANLkTi=Gey75oo-iaELVWg87cP+HgM3RQ60vPgwaEMpS@mail.gmail.com>
On Wed, 26 Jan 2011, Mika Fischer wrote:
> curl/openssl 0.9.8k <-> apache/openssl 1.0.0 -> error
> I'm not sure what to take away from this. Maybe it's a problem that is
> partly caused by both apache and curl?
Could be. I just have a hard time to see why code in curl that has worked for
so many years suddenly would stop working. It just so feels like else changed.
This error (or something similar to it) is often seen when we try to talk
plain HTTP to a HTTPS server or vice versa. Did you verify that HTTPS was
working fine on that port when you ran the OpenSSL 1.0.0 version of the
server?
Perhaps it is possible to add verbose level and further debug log stuff in the
server to see what makes it suddenly decide the handshake is bad.
--
/ daniel.haxx.se
next prev parent reply other threads:[~2011-01-26 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0aa77107-bb31-4f74-90e2-02ce5155b0a0@l17g2000yqe.googlegroups.com>
2011-01-25 19:05 ` [msysGit] Git unable to access https repositories due to curl/OpenSSL 1.0.0 handshake issues Erik Faye-Lund
2011-01-26 9:15 ` Mika Fischer
2011-01-26 9:54 ` Mika Fischer
2011-01-26 9:57 ` Daniel Stenberg
2011-01-26 10:04 ` Mika Fischer
2011-01-26 13:29 ` Daniel Stenberg
2011-01-26 14:29 ` Erik Faye-Lund
2011-01-26 15:13 ` [msysGit] " Mika Fischer
2011-01-26 22:00 ` Daniel Stenberg [this message]
2011-01-26 22:18 ` Mika Fischer
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.1101262244550.14066@tvnag.unkk.fr \
--to=daniel@haxx.se \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=mika.a.fischer@googlemail.com \
--cc=msysgit@googlegroups.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).