[
https://issues.apache.org/jira/browse/TS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1127:
------------------------------
Fix Version/s: (was: 3.1.3)
3.1.4
> Wrong returned value of incoming port address
> ---------------------------------------------
>
> Key: TS-1127
> URL: https://issues.apache.org/jira/browse/TS-1127
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 3.1.2
> Reporter: Yakov Kopel
> Assignee: Alan M. Carroll
> Fix For: 3.1.4
>
> Attachments: fix.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> The API TSHttpTxnClientIncomingPortGet has been changed in Wed Oct 5 19:14:07
> 2011 (TS-926) and it returns another value.
> in the old version it returned the incoming port of the TS(the port which the
> client connected to the TS).
> in the new version the returned value is the sending port of the user.
> The different is in the line:
> - return sm->t_state.client_info.port;
> + return ink_inet_get_port(&sm->t_state.client_info.addr);
> The assignment of those two members (port, addr) are in the HttpSM.cc file
> ink_inet_copy(&t_state.client_info.addr, netvc->get_remote_addr());
> t_state.client_info.port = netvc->get_local_port();
>
> The old code gave the right answer from the port member, and the new one
> gives us wrong answer from the remote address.
> I attached a patch to fix this returned value.
--
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
