[
https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614715#comment-13614715
]
Scott Harris commented on TS-1767:
----------------------------------
Sure thing.
I have added into records.config
CONFIG proxy.config.http_ui_enabled INT 3
in remap.config
map http://<server>:<port>/cache/ http://{cache}
Then I go to http://<server>:<port>/cache/
select option "Regex lookup" (uri /cache/lookup_regex_form)
I use http:// (the default) as the regex search to retrieve all cached objects
and the returned objects and links all refer back to origin server url not the
incoming url and selecting any results in "Cache Lookup Failed, or missing in
cluster"
ie
if incoming url is http://incoming/static/1.jpg and this is mapped to origin
server http://origin/static/1.jpg
The regex lookup url above returns http://origin/static/1.jpg. The link refer
to http://<server>:<port>/cache/lookup_url?url=http://origin/static/1.jpg. If
I change this url to
http://<server>:<port>/cache/lookup_url?url=http://incoming/static/1.jpg it
returns the info on the cache object.
Since all the objects are referenced by the incoming url (/cache/lookup_url
shows this) I would expect the regex lookup to return incoming urls not origin
urls.
Scott
> 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 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
