[
https://issues.apache.org/jira/browse/TS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652749#comment-14652749
]
ASF subversion and git services commented on TS-3376:
-----------------------------------------------------
Commit 6062188f57efa48d6208311ff4d111d41b7cd93b in trafficserver's branch
refs/heads/6.0.x from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=6062188 ]
Merge branch 'master' into 6.0.x
* master:
TS-3796: health check fails once during startup
Revert "TS-3376: traffic_server failed assert
s->current.server->had_connect_fail()"
TS-3376: traffic_server failed assert s->current.server->had_connect_fail()
TS-3810 traffic_manager leaks that thread stack, make sure to detach the
threads
Revert "TS-3810 traffic_manager leaks that thread stack, make sure to detach
the threads"
TS-3810 traffic_manager leaks that thread stack, make sure to detach the
threads
> Missing cert chain file gives no errors or warnings
> ---------------------------------------------------
>
> Key: TS-3376
> URL: https://issues.apache.org/jira/browse/TS-3376
> Project: Traffic Server
> Issue Type: Improvement
> Components: SSL
> Reporter: Leif Hedstrom
> Assignee: Susan Hinrichs
> Fix For: 5.3.0
>
>
> With an ssl_multicert.config of
> {code}
> {code}
> ATS will start up without any (as far as I could tell) errors, even when the
> cert chain file is completely missing. It just silently accepts the config,
> and brings ATS up in a poor state as far as TLS is concerned.
> IMO, we should at a minimum write some very serious warnings and errors on
> this, but maybe even refuse to startup (or reload) the config if the cert
> chain file is missing. This is serious enough that the server is in a
> non-functional state if it happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
