You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2011/07/31 05:56:10 UTC

[jira] [Updated] (TS-802) Unique KA pools for SOCKS/src IP parameters

     [ 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.0)
                   3.1.1

> 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.1.1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira