You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/18 16:23:20 UTC
[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used
[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25641&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25641 ]
ASF GitHub Bot logged work on TS-4622:
--------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jul/16 16:22
Start Date: 18/Jul/16 16:22
Worklog Time Spent: 10m
Work Description: Github user jacksontj commented on the issue:
https://github.com/apache/trafficserver/pull/773
Yea, I'll have to look a bit more. Ideally its as close to that DNS lookup as possible, that way if some plugin wants to overwrite it I've done the change in core before they can (so that we won't be clobbering eachother). Have to look into it this week.
Issue Time Tracking
-------------------
Worklog Id: (was: 25641)
Time Spent: 10m
Remaining Estimate: 0h
> 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: 10m
> 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)