You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2022/09/02 20:41:00 UTC

[jira] [Resolved] (THRIFT-5617) T(SSL)Socket TCP keep-alive incorrectly applies SO_KEEPALIVE to IPPROTO_TCP

     [ https://issues.apache.org/jira/browse/THRIFT-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer resolved THRIFT-5617.
--------------------------------
    Fix Version/s: 0.18.0
         Assignee: Nick Withers
       Resolution: Fixed

> T(SSL)Socket TCP keep-alive incorrectly applies SO_KEEPALIVE to IPPROTO_TCP
> ---------------------------------------------------------------------------
>
>                 Key: THRIFT-5617
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5617
>             Project: Thrift
>          Issue Type: Bug
>          Components: Python - Library
>            Reporter: Nick Withers
>            Assignee: Nick Withers
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 0.18.0
>
>   Original Estimate: 1h
>          Time Spent: 20m
>  Remaining Estimate: 40m
>
> {{SO_KEEPALIVE}} is a {{SOL_SOCKET}}-level socket option.
> At least on my (Linux-based) system, this causes {{IPPROTO_TCP}} {{TCP_DEFER_ACCEPT}} to be set to 1 when a {{T(SSL)Socket}} is created with {{socket_keepalive}} set and keep-alives are not enabled.
> See also: https://man7.org/linux/man-pages/man7/socket.7.html , https://docs.microsoft.com/en-us/windows/win32/winsock/so-keepalive



--
This message was sent by Atlassian Jira
(v8.20.10#820010)