Hi Thomas,
Putting the trailing slash did indeed fix that.
I got that from the Administrators guid here :
http://trafficserver.readthedocs.org/en/latest/admin/configuring-cache.en.html
so there is a typo that does not include the trailing slash.
And thank you for letting me know that the issue already has an
outstanding ticket for the web ui. Although it does look like there has
not been any work on it, even though it seems like it would be an easy fix.
Thanks,
Tim
On 1/31/14, 4:01 AM, Thomas Berger wrote:
Hi Tim,
for the first problem, i think you have to add a trailing slash to the target
url:
map http://domain.com/myCI/ http://{cache}
The second one is a known bug:
https://issues.apache.org/jira/browse/TS-1767
Am Donnerstag, 30. Januar 2014, 12:13:20 schrieb Tim Traver:
Hi All,
ok, I got the cache ui running and can access it, but the first page
doesn't give the proper URL's for the different functionality.
I have the following setting:
map http://domain.com/myCI http://{cache} @action=allow
@src_ip=xxx.xxx.xxx.xxx
Now, when I go to the ui with this URL http://domain.com/myCI I get the
initial cache page that has four links on it for the four functions. But
when I click on one of them, it is trying to go to
http://domain.com/lookup_url_form which is an invalid URL.
I figure out if I went to http://domain.com/myCI/lookup_url_form that I
would indeed get to the lookup form. But all of the links on that front
page are like that...
Also, it appears that once I get a list of URL's that they are built
with the origin's hostname, not the hostname that is in the cache. I saw
on another post somewhere that using
theproxy.config.url_remap.pristine_host_hdr may effect this. In the
cache URL if I change the host of the object it is looking up, then I
find the cache entry and its information.
Maybe this is already a known issue, but if there are any configuration
directives that might solve it, I would be greateful to hear them...
Thanks,
Tim
