[
https://issues.apache.org/jira/browse/TS-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912244#comment-13912244
]
James Peach commented on TS-382:
--------------------------------
The right thing to do here is to parse supported socket option strings, e.g.:
{code}
CONFIG proxy.config.net.sock_option_flag_out STRING TCP_NODELAY TCP_QUICKACK
{code}
> 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: 6.0.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 was sent by Atlassian JIRA
(v6.1.5#6160)
