You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Igor Galić (Commented JIRA)" <ji...@apache.org> on 2011/11/10 23:03:51 UTC

[jira] [Commented] (TS-462) Support TLS Server Name Indication (SNI) negotiation

    [ https://issues.apache.org/jira/browse/TS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148044#comment-13148044 ] 

Igor Galić commented on TS-462:
-------------------------------

We've come to the using conclusion that putting the whole thing into {{remap.config}} is not quite sensible.

However, putting it into {{ssl_multicert.config}} is. e.g.:
{noformat}
src_domain=secure.apache.org ssl_cert_name=secure.a.o.cert ssl_key_name=secure.a.o.key
src_domain=shop.openoffice.org ssl_cert_name=shop.ooo.cert ssl_key_name=shop.ooo.key
{noformat}
                
> Support TLS Server Name Indication (SNI) negotiation
> ----------------------------------------------------
>
>                 Key: TS-462
>                 URL: https://issues.apache.org/jira/browse/TS-462
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: SSL
>    Affects Versions: 3.0.0
>            Reporter: Leif Hedstrom
>            Assignee: Igor Galić
>            Priority: Minor
>              Labels: ssl
>             Fix For: 3.1.4
>
>
> We should support TLS Server Name Indication (SNI). This would allow for well behaved TLS clients to negotiate the certificate, without requiring a new IP for every site / certificate used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira