[
https://issues.apache.org/jira/browse/TS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220100#comment-13220100
]
Leif Hedstrom commented on TS-462:
----------------------------------
Subject Alternatative Name or some such. Basically, you can have > 1 domain in
a cert, other than the mandatory domain. E.g.
X509v3 Subject Alternative Name:
DNS:*.foo.com, DNS:*.bar.com, DNS:*.fie.org
I don't think it's always been in the specs, but I've used this for a long time
for my private certs. If I recall (I'm probably wrong), you used to have to put
multiple names in the CN.
Also, http://tools.ietf.org/html/rfc6125 tries to clarify all those I think.
> 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.5
>
>
> 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