> Up to version 2.0.x the answer is that there is no support for it. > For 2.1.x there might be some initial code to take care of that, but even if > it did make it into the tree, then it is more or less untested because there > are no clients for it.
Interesting answer. Thanks! I asked this because I need to write an SSL-aware HTTP client. Whatever, I am now wondering how strong is the pressure to migrate from the classical "https" scheme to the "client requested upgrade" (as I see these as somehow alternatives, as the client explicitely request "https"...). As far as I understand, RFC 2817 (May 2000...) clearly states that things like HTTPS should be deprecated. So I wonder what the "market" says... You say there is no client: am I really going to write the first one that supports this? As apache starts to support it, I guess there might be some other people looking fot it also. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.516 / Virus Database: 313 - Release Date: 01/09/2003 ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
