Changeset 1891

Show
Ignore:
Timestamp:
08/21/08 19:39:25 (3 months ago)
Author:
taher
Message:

--

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • cherokee/trunk/doc/bundle_cget.txt

    r1816 r1891  
    99tool. You might find it useful for your own scripts, especially for 
    1010its ability to read and write HTTP headers. 
     11 
     12It can handle both HTTP and HTTPS requests. 
    1113 
    1214This is the full information provided by the manpage: 

  • cherokee/trunk/doc/config_virtual_servers.txt

    r1816 r1891  
    337337before using secure connections (https). There is a document which 
    338338might help to generate SSL link:cookbook_ssl.html[keys] 
     339 
     340Cherokee fully supports the usage of different certificates for each 
     341virtual server in a given host, be it using SNI as defined in 
     342link:http://www.rfc-archive.org/getrfc.php?rfc=3546[RFC 3546] or by 
     343elegantly respinning the secure handshake. 

  • cherokee/trunk/doc/other_goodies.txt

    r1844 r1891  
    9393~~~~~~~~~~~~~~~~~ 
    9494You might have been told elsewhere that named virtual hosts in SSL 
    95 cannot be supported because a web server cannot see the hostname 
    96 header when the SSL request is being processed. Technically this might 
    97 have been correct in the past. The first thing that the server has to 
    98 do is to connect with the other end by using SSL/TLS, so at that 
    99 point, before it receives the HTTP client request, the crypto 'magic' 
    100 already needs to have happened. 
     95cannot be supported without SNI (Server Name Indication) because a web 
     96server cannot see the hostname header when the SSL request is being 
     97processed. Technically this might have been correct in the past. The 
     98first thing that the server has to do is to connect with the other end 
     99by using SSL/TLS, so at that point, before it receives the HTTP client 
     100request, the crypto 'magic' already needs to have happened. 
    101101 
    102102However, nothing is forever.. and that applies to SSL/TLS connections 
    …… 
    104104virtual server, and the magic occurs: SSL supporting several 
    105105certificates on the same IP address and port. 
     106 
     107If SNI is supported by your SSL/TLS library, nothing of this needs to 
     108happen because the host info can be put in the SSL handshake. Things 
     109will simply work as long as there is a web browser with SNI support at 
     110the other side. Currently every modern web browser supports this.