[
https://issues.apache.org/jira/browse/TS-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345339#comment-14345339
]
ASF subversion and git services commented on TS-3414:
-----------------------------------------------------
Commit cd60e20bd4b554930a4d6eef77762154f5b1aed8 in trafficserver's branch
refs/heads/master from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=cd60e20 ]
[TS-3414]: Update docs for TSHttpTxnOutgoingAddrGet and TSHttpTxnIncomingAddrGet
> 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)
