[ 
https://issues.apache.org/jira/browse/TS-4882?focusedWorklogId=29471&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29471
 ]

ASF GitHub Bot logged work on TS-4882:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Sep/16 23:43
            Start Date: 21/Sep/16 23:43
    Worklog Time Spent: 10m 
      Work Description: Github user bryancall commented on a diff in the pull 
request:

    https://github.com/apache/trafficserver/pull/1036#discussion_r79950331
  
    --- Diff: doc/admin-guide/files/records.config.en.rst ---
    @@ -3388,13 +3388,19 @@ Sockets
             TCP_NODELAY  (1)
             SO_KEEPALIVE (2)
             SO_LINGER (4) - with a timeout of 0 seconds
    +        TCP_FASTOPEN (8)
     
     .. note::
     
        This is a bitmask and you need to decide what bits to set.  Therefore,
        you must set the value to ``3`` if you want to enable nodelay and
        keepalive options above.
     
    +.. note::
    +
    +   To allow TCP Fast Open for client sockets on Linux, bit 2 of
    --- End diff --
    
    Isn't it bit 1 for client sessions or a value of 1?  That should be the 
default on most linux distros.


Issue Time Tracking
-------------------

    Worklog Id:     (was: 29471)
    Time Spent: 1h 40m  (was: 1.5h)

> TCP Fast Open support for SSL server sessions.
> ----------------------------------------------
>
>                 Key: TS-4882
>                 URL: https://issues.apache.org/jira/browse/TS-4882
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core, SSL
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 7.1.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Add support for using TCP Fast Open on TLS server sessions. This is mainly 
> interesting for CONNECT tunnels where we can't use long running persistent 
> sessions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to