[
https://issues.apache.org/jira/browse/TS-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507401#comment-14507401
]
ASF subversion and git services commented on TS-3529:
-----------------------------------------------------
Commit bf4ba0cf2741d7d189deba608154b07aa61dce46 in trafficserver's branch
refs/heads/5.3.x from shinrich
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=bf4ba0c ]
TS-3529: Add a config to allow ATS to start up even if some certificates are
bad.
(cherry picked from commit ef36a509c0a3cf0309ad563e980d7e002f9b2d9c)
Conflicts:
CHANGES
> Add a config option to allow ATS to start even if some certificates are bad
> ---------------------------------------------------------------------------
>
> Key: TS-3529
> URL: https://issues.apache.org/jira/browse/TS-3529
> Project: Traffic Server
> Issue Type: Bug
> Components: SSL
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Priority: Blocker
> Fix For: 5.3.0, 6.0.0
>
>
> In fixing TS-3329, we changed the ATS start up behavior to fail to start if
> any of the entries of ssl_multicert.config fails to load. This changes the
> functionality of ATS in from 5.2 to 5.3.
> For many/most use cases, this is a desirable change. However, for some use
> cases, you want to serve and start up even if some of the entries fail to
> load.
> We will add a records config entry
> proxy.config.ssl.server.multicert.exit_on_load_fail
> It will default to 1 on 5.x. May want to change the default to 0 when we
> move to 6.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
