[ https://issues.apache.org/jira/browse/TS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615690#comment-13615690 ]
Leif Hedstrom commented on TS-382: ---------------------------------- I do think it's useful to support these (and as many as possible) of these TCP options. > 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 > 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