[
https://issues.apache.org/jira/browse/TS-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3501:
------------------------------
Fix Version/s: 6.0.0
> Support configuring nagle for client sockets using
> {{proxy.config.net.sock_option_flag_in}}
> -------------------------------------------------------------------------------------------
>
> Key: TS-3501
> URL: https://issues.apache.org/jira/browse/TS-3501
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
> Reporter: Sudheer Vinukonda
> Assignee: Sudheer Vinukonda
> Fix For: 6.0.0
>
>
> https://docs.trafficserver.apache.org/en/latest/reference/configuration/records.config.en.html#proxy-config-net-sock-option-flag-in
> describes a setting {{proxy.config.net.sock_option_flag_in}} to allow
> enabling/disabling nagle algorithm on client (to ATS) sockets. However,
> there's no code to handle the setting for the client socket and currently,
> the client socket defaults to enabling Nagle. Opening this jira to make the
> enhancement to allow configuring Nagle on the client socket.
> Note that the client socket option needs to be set in two places
> (NetAccept::acceptFastEvent or the caller for when accept threads are
> disabled and Server::accept when accept threads are enabled).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
