You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2013/03/29 15:52:14 UTC

[jira] [Assigned] (TS-382) socket option "cleanup" (and bug fixes)

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

Alan M. Carroll reassigned TS-382:
----------------------------------

    Assignee: Alan M. Carroll
    
> socket option "cleanup" (and bug fixes)
> ---------------------------------------
>
>                 Key: TS-382
>                 URL: https://issues.apache.org/jira/browse/TS-382
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Network
>            Reporter: Leif Hedstrom
>            Assignee: Alan M. Carroll
>             Fix For: 3.5.0
>
>
> This is a bug moved from Y! Bugzilla, I'm posting the original bug description and a few comments separately. Note that the bug description is fairly limited, but while looking at this code, I noticed a lot of oddities with the "socket option" support (lots of hardcoded stuff, and most of it is not configurable).
> Note that the original bug should have been fixed already in Apache TS, but the other comments are still applicable.
> From Bugzilla (posted by Leif):
> We have two socket option config options in records.config:
> proxy.config.net.sock_option_flag_in
> proxy.config.net.sock_option_flag_out
> With accept thread enabled, at least the _in option isn't honored. There are possibly other cases in UnixNetAccept.cc
> that we don't honor these flags either.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira