[
https://issues.apache.org/jira/browse/TS-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-802:
-----------------------------
Fix Version/s: (was: 3.1.5)
3.3.0
Moving this out to 3.3.0, please move back to 3.1.4 if this will be worked on
*soon*. Also, take a look at what can be closed here please!
> 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
> Reporter: M. Nunberg
> Fix For: 3.3.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
