You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2015/03/03 17:51:04 UTC

[jira] [Updated] (TS-3414) New API for Outgoing Address

     [ https://issues.apache.org/jira/browse/TS-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudheer Vinukonda updated TS-3414:
----------------------------------
    Affects Version/s: 5.3.0
        Fix Version/s: 5.3.0
             Assignee: Sudheer Vinukonda

>  New API for Outgoing Address
> -----------------------------
>
>                 Key: TS-3414
>                 URL: https://issues.apache.org/jira/browse/TS-3414
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: TS API
>    Affects Versions: 5.3.0
>            Reporter: Sudheer Vinukonda
>            Assignee: Sudheer Vinukonda
>             Fix For: 5.3.0
>
>
> There's currently no TS API to retrieve the source address used by the proxy in the outbound connections. 
> I would like to add a new TS API that can provide this info - In addition to making it consistent with the API for inbound addresses (where we have TS API for both remote and local addresses), there may be other use cases that need this info (e.g. applying rate limiting on the inbound side based on the ephemeral ports).
> tsapi struct sockaddr const* TSHttpTxnOutgoingAddrGet(TSHttpTxn txnp);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)