[ 
https://issues.apache.org/jira/browse/TS-4875?focusedWorklogId=29634&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29634
 ]

ASF GitHub Bot logged work on TS-4875:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Sep/16 18:24
            Start Date: 23/Sep/16 18:24
    Worklog Time Spent: 10m 
      Work Description: GitHub user jpeach opened a pull request:

    https://github.com/apache/trafficserver/pull/1043

    TS-4875: Be more robust against SSL_new() failure.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jpeach/trafficserver update/4875

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/1043.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1043
    
----
commit db27c4a0b21c21c14997fdd4e310dbd8ec9ddd04
Author: James Peach <[email protected]>
Date:   2016-09-23T18:23:19Z

    TS-4875: Be more robust against SSL_new() failure.

----


Issue Time Tracking
-------------------

    Worklog Id:     (was: 29634)
    Time Spent: 1h 50m  (was: 1h 40m)

> Hoist SSL index creation into library initialization.
> -----------------------------------------------------
>
>                 Key: TS-4875
>                 URL: https://issues.apache.org/jira/browse/TS-4875
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: SSL
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 7.1.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The SSL index used for server certificate validation can only be created 
> once, so we need to do it in the library initialization, not the client 
> context initialization. In principle, we can initialize client contexts 
> multiple times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to