[
https://issues.apache.org/jira/browse/TS-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101904#comment-15101904
]
ASF GitHub Bot commented on TS-3527:
------------------------------------
Github user shinrich commented on the pull request:
https://github.com/apache/trafficserver/pull/402#issuecomment-171990184
Yes, I agree that having a matching TSSslContextDestroy is a good idea even
if it is just a wrapper for the openssl call at this point.
I also like the idea of adding hook points to aid in coordination of
session ticket handling. I had proposed something similar for coordinating ssl
session state between servers (TS-3527). I had initial code but met with
resistance to the idea and got pulled into other things. But I'd be very
interested in coming back to that and making session restarts work better in a
multi-server environment.
> Add plugin hooks for SSL Session state access
> ---------------------------------------------
>
> Key: TS-3527
> URL: https://issues.apache.org/jira/browse/TS-3527
> Project: Traffic Server
> Issue Type: Improvement
> Components: SSL
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 6.2.0
>
>
> Add plugin hook functionality to allow hook into the SSL session state
> lifecycle. This enables session state communication between ATS deployments
> and additional statistical analysis.
> One API proposal is at
> http://network-geographics.com/ats/docs/ssl-session-api.en.html
> [~briang] suggested merging this with the existing TS_SSL_SNI_HOOK. Will
> have to look in more detail with the openssl implementations to see if we can
> hook into to a single point that has access to the functionality needed by
> both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
