[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25757&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25757 ]
ASF GitHub Bot logged work on TS-4622: -------------------------------------- Author: ASF GitHub Bot Created on: 20/Jul/16 14:58 Start Date: 20/Jul/16 14:58 Worklog Time Spent: 10m Work Description: Github user jacksontj commented on the issue: https://github.com/apache/trafficserver/pull/773 @jpeach I did some testing of my own and I can't reproduce any problems with `TsHttpTxnServerAddrSet()` at all. TSHttpTxnServerAddrSet() is supposed to be called before the DNS lookup. If called then the core bypasses the entire OS_DNS stuff which includes this port setting block in HttpTransact. I tested calling the API on both the `TS_EVENT_HTTP_READ_REQUEST_HDR` and `TS_EVENT_HTTP_OS_DNS` hooks-- with no problem at all. You mentioned in a previous comment that it was broken in your testing, can you share the code you were using to see it broken? Issue Time Tracking ------------------- Worklog Id: (was: 25757) Time Spent: 1.5h (was: 1h 20m) > Ports from SRV lookups aren't used > ---------------------------------- > > Key: TS-4622 > URL: https://issues.apache.org/jira/browse/TS-4622 > Project: Traffic Server > Issue Type: Bug > Components: DNS > Reporter: Thomas Jackson > Assignee: Thomas Jackson > Fix For: 7.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Although the dns processor parses out the ports and we keep track of them, it > seems that the port from the SRV response is not used at all when connecting > to the origin. Simple fix, we simply need to set the port before doing > `do_http_server_open` (potentially earlier if we want to let plugins etc. > override the port?) -- This message was sent by Atlassian JIRA (v6.3.4#6332)