[
https://issues.apache.org/jira/browse/TS-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911322#comment-13911322
]
Wei Sun commented on TS-2437:
-----------------------------
Thanks for the committing. I think the default ssl_ctx is necessary since
client presenting a ticket will go into the ticket_callback which is prior to
SNI callback, at that time the default ssl_ctx is attached to the request. If
the default ssl_ctx is not exposed to application and is not able to register
ticket_callback, ticket reuse will be skipped... A similar issue is in
https://issues.apache.org/jira/browse/TS-2480?focusedCommentId=13874730&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13874730
> Add an API to expose SSL_CTX for applications
> ---------------------------------------------
>
> Key: TS-2437
> URL: https://issues.apache.org/jira/browse/TS-2437
> Project: Traffic Server
> Issue Type: Task
> Components: SSL, TS API
> Reporter: Wei Sun
> Assignee: James Peach
> Labels: Review
> Fix For: 5.0.0
>
> Attachments: TS-2437-2.diff, TS-2437-liefecycle-2.diff
>
>
> It'll be good to add an API to expose all the SSL_CTXs, so that plugins can
> manipulate their specific ssl settings / call back, etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
