Changeset 1839

Show
Ignore:
Timestamp:
08/15/08 01:08:09 (3 months ago)
Author:
taher
Message:

--

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • cherokee/trunk/doc/other_goodies.txt

    r1816 r1839  
    8888With Cherokee you can cope with this and much more. With Cherokee, its 
    8989easier done than said. 
     90 
     91[[ssl-vhosts]] 
     92SSL Virtual Hosts 
     93~~~~~~~~~~~~~~~~~ 
     94You might have been told elsewhere that named virtual hosts in SSL 
     95cannot be supported because a web server cannot see the hostname 
     96header when the SSL request is being processed. Technically this might 
     97have been correct in the past. The first thing that the server has to 
     98do is to connect with the other end by using SSL/TLS, so at that 
     99point, before it receives the HTTP client request, the crypto 'magic' 
     100already needs to have happened. 
     101 
     102However, nothing is forever.. and that applies to SSL/TLS connections 
     103as well. Cherokee elegantly respins the SSL layer once it knows the 
     104virtual server, and the magic occurs: SSL supporting several 
     105certificates on the same IP address and port.