You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Scott Harris (JIRA)" <ji...@apache.org> on 2013/03/21 04:29:15 UTC
[jira] [Updated] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Harris updated TS-1767:
-----------------------------
Description:
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
was:
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
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira