[
https://issues.apache.org/jira/browse/TS-4856?focusedWorklogId=29016&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29016
]
ASF GitHub Bot logged work on TS-4856:
--------------------------------------
Author: ASF GitHub Bot
Created on: 13/Sep/16 22:32
Start Date: 13/Sep/16 22:32
Worklog Time Spent: 10m
Work Description: Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/pull/1013
Took @jpeach's suggestion and pulled back a bit. Moved the missing cert
check out of SSLInitServerContext and made the check at the one call site that
actually parses the ssl multicert.
Issue Time Tracking
-------------------
Worklog Id: (was: 29016)
Time Spent: 50m (was: 40m)
> Default SSL context fails to load.
> ----------------------------------
>
> Key: TS-4856
> URL: https://issues.apache.org/jira/browse/TS-4856
> Project: Traffic Server
> Issue Type: Bug
> Components: SSL
> Reporter: James Peach
> Assignee: Susan Hinrichs
> Fix For: 7.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This error message appears at startup:
> {noformat}
> [Sep 12 21:07:16.700] Server {0x7f98127d9780} ERROR: failed set default
> context
> {noformat}
> Out of source context, this error is not especially grammatical.
> The problem seems to be a regression from TS-4671, since the default {{*}}
> certificate fails to be constructed in {{SSLInitServerContext}} due to the
> tunnel options check. The default context has neither a certificate nor a
> tunnel option.
> AFAIK we still need a default certificate to make the TLS negotiation fail
> when we don't get an actual certificate match.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
