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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
