[ 
https://issues.apache.org/jira/browse/TS-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353786#comment-15353786
 ] 

ASF GitHub Bot commented on TS-3371:
------------------------------------

GitHub user persiaAziz opened a pull request:

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

    TS-3371: Global variable for enabling SSL session ticket

    Global variable proxy.config.ssl.server.session_ticket.enable added to 
enable/disable the usage of SSL session ticket

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

    $ git pull https://github.com/persiaAziz/trafficserver TS-3371

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

    https://github.com/apache/trafficserver/pull/758.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 #758
    
----
commit 986e56bb542e662329d267ff1ee73c28d7ee8510
Author: Syeda Aziz <per...@kickedpredict.corp.ne1.yahoo.com>
Date:   2016-06-27T16:40:51Z

    TS-3371: Programmatic disabling of SSL ticket use.
    
    unwanted changes removed

----


> 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)

Reply via email to