[
https://issues.apache.org/jira/browse/TS-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach updated TS-802:
---------------------------
Component/s: SOCKS
> Unique KA pools for SOCKS/src IP parameters
> -------------------------------------------
>
> Key: TS-802
> URL: https://issues.apache.org/jira/browse/TS-802
> Project: Traffic Server
> Issue Type: Wish
> Components: HTTP, SOCKS
> Reporter: M. Nunberg
>
> From what I've observed, ATS' keepalive/connection cache only indexes by the
> OS server or next proxy server, but not by other types of
> connection/transport/socket parameters, specifically in my case, negotiated
> SOCKS connections and outgoing connections which are bound to a specific
> source IP
> Is it possible to have such functionality in the near future? Currently I've
> been forced to write my own 'KA gateway' which pretends to be an HTTP server
> (to which ATS can maintain unique connections) and have that do SOCKS/source
> ip bind()ing for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
