On Tue, 10 Aug 2010, Matthieu Speder wrote:
We could (or should?) perhaps do the same when a custom Host: is used and
an SNI name is passed on, as then (lib)curl would still do the proper SNI
even when trying out a local https:// site like above.
Agree. And by the way I think that this might be the right thing to do
anyway, even without my strange context. The only restriction I see is that
HTTP header is only relevant for HTTP service while TLS SNI could in theory
apply to non HTTP also. However, in real life, I'm not aware of any TLS
server really using SNI apart from HTTPS servers.
I looked for a way to implement your idea.
I know this was discussed quite a while ago, but is there any chance you will
work on implementing this?
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
