[
https://issues.apache.org/jira/browse/TS-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344922#comment-15344922
]
Susan Hinrichs commented on TS-3371:
------------------------------------
I thought what we had decided from the Fall 2015 summit was to add a global
ticket file config in records.config. Then if necessary, fix the
ssl_multicert.config entries as overrides. But as I recall, there didn't seem
to be a need at this point for changing ticket keys on a per domain basis.
If the setting is global, there is no lookup issue.
http://network-geographics.com/assets/docs/PostFall2015SummitSSLnotes.pdf
> Should create a global session ticket disable
> ---------------------------------------------
>
> Key: TS-3371
> URL: https://issues.apache.org/jira/browse/TS-3371
> Project: Traffic Server
> Issue Type: Bug
> Components: SSL
> Reporter: Susan Hinrichs
> Assignee: Syeda Persia Aziz
> Fix For: sometime
>
>
> The current implementation requires the user to set the ssl_ticket_enabled=0
> for every entry in ssl_multiserver.config to turn off the ssl ticket session
> support.
> It would be better to have a global switch. It seems highly unlikely that
> someone will want to deploy ssl tickets for some destinations but not others.
> Would also be good to have a switch to disable ATS from offering session
> tickets when communicating with origin servers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
