| | 90 | |
|---|
| | 91 | [[ssl-vhosts]] |
|---|
| | 92 | SSL Virtual Hosts |
|---|
| | 93 | ~~~~~~~~~~~~~~~~~ |
|---|
| | 94 | You 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. |
|---|
| | 101 | |
|---|
| | 102 | However, nothing is forever.. and that applies to SSL/TLS connections |
|---|
| | 103 | as well. Cherokee elegantly respins the SSL layer once it knows the |
|---|
| | 104 | virtual server, and the magic occurs: SSL supporting several |
|---|
| | 105 | certificates on the same IP address and port. |
|---|