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ć (JIRA)" <ji...@apache.org> on 2011/07/20 01:27:57 UTC
[jira] [Commented] (TS-462) [GSoc2011] 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=13068063#comment-13068063 ]
Igor Galić commented on TS-462:
-------------------------------
Leif suggested to solve this via {{remap.config}}, it does sound sane. We'd then have a setup such as:
{noformat}
map https://secure.example.org/ http://example.org/ @sni_cert=sec.example.pem @sni_key=sec.example.key
map https://intra.example.org/ https://internal.example.org/ @sni_cert=int.example.pem @sni_key=int.example.key
map https://ssi.example.com/ http://ssi.example.internal/ @sni_cert=ssi.example.pem @sni_key=ssi.example.key
{noformat}
> [GSoc2011] 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
> Reporter: Leif Hedstrom
> Priority: Minor
> Labels: gsoc2011, ssl
> Fix For: 3.1.1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira