[
https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885514#comment-13885514
]
Thomas Berger commented on TS-1767:
-----------------------------------
Is i found this problem very annoying, i had a look.
What i found so far:
The helper class UrlPrintHack should prepare the URL Object for the printing
process.
It should set the Host in the Url string from the Host header. For some reasons
{code}hdr->m_target_in_url{code} seems to be true, so that the host is not set
from the header.
I will investigate this issue, unless someone is already working on this and
want to finish it.
> Cache Lookup Regex using incorrect urls
> ---------------------------------------
>
> Key: TS-1767
> URL: https://issues.apache.org/jira/browse/TS-1767
> Project: Traffic Server
> Issue Type: Bug
> Components: Web UI
> Reporter: Scott Harris
> Fix For: sometime
>
>
> When using the cache regex lookup returned urls contain origin server not of
> incoming mapping to ats.
> Ie using map http://incoming http://10.1.1.1:8080
> returned regex urls are : http://10.1.1.1:8080/<blah> instead of
> http://incoming/<blah>
> Selecting any of these results in "Cache Lookup Failed, or missing in cluster"
> Doing url lookup with incoming url returns valid result.
> Using version 3.2.4 running as a reverse proxy
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
