[
https://issues.apache.org/jira/browse/TS-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245396#comment-13245396
]
James Peach commented on TS-1147:
---------------------------------
Only the .filename options have been removed.
I added explicit support for this in ssl_multicert:
dest_ip=* ssl_cert_name=foo.crt
No it doesn't. If we can't find a certificate we will just fail the connection.
In my branch, the behaviour is to complete the SSL handshake using the default
certificate. If the client accepts this, then there's no reason to return a 400.
> deprecate records.config SSL configuration
> ------------------------------------------
>
> Key: TS-1147
> URL: https://issues.apache.org/jira/browse/TS-1147
> Project: Traffic Server
> Issue Type: Improvement
> Components: SSL
> Reporter: James Peach
> Assignee: James Peach
> Priority: Minor
> Fix For: 3.1.5
>
>
> Since ssl_multicert.config is a strict superset of the SSL certificate
> configuration in records.config, we should deprecate configuring SSL
> certificates in records.config and make ssl_multicert.config the One True Way.
--
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
