[
https://issues.apache.org/jira/browse/TS-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353117#comment-15353117
]
ASF GitHub Bot commented on TS-3371:
------------------------------------
Github user shinrich commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/750#discussion_r68771592
--- Diff: mgmt/RecordsConfig.cc ---
@@ -1212,6 +1212,8 @@ static const RecordElement RecordsConfig[] =
//##############################################################################
{RECT_CONFIG, "proxy.config.ssl.enabled", RECD_INT, "0",
RECU_RESTART_TS, RR_NULL, RECC_INT, "[0-1]", RECA_NULL}
,
+ {RECT_CONFIG, "proxy.config.ssl.session.ticket.enabled", RECD_INT, "1",
RECU_RESTART_TS, RR_NULL, RECC_INT, "[0-1]", RECA_NULL}
--- End diff --
I like proxy.config.ssl.server.ticket_key.enabled. I think you can
enable/disable tickets on client side and server side, so I think it is good to
be explicit in case we want to support client side changing advertising ticket
capability.
> 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 ATS to set the ssl_ticket_enabled=0
> for every entry in ssl_multicert.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)
