[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989126#comment-14989126 ] Christoph Keller commented on TS-1767: -- I wrote a little hack for that issue. It's definitely not a real fix but at least it kinda works with it. http://pastebin.com/HgBHi8S6 If you got a lot of stuff in your cache it still suddenly crashes. In my test that happened with about 8 different documents in cache. Obviously it crashed due to a failing assertion. I still don't get it why that assertion fails. It's in HdrHeap::allocate_str (ink_assert(m_writeable);). If i remove it everything seems to work fine. Can anybody explain what could possibly make that assertion fail? Anybody got some advice on how to improve that patch? > 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/ instead of > http://incoming/ > 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.3.4#6332)
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[
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/ instead of
> http://incoming/
> 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)
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614881#comment-13614881 ] Scott Harris commented on TS-1767: -- Understand, thanks. 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 >Assignee: Leif Hedstrom > Fix For: 3.3.3 > > > 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/ instead of > http://incoming/ > 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
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614875#comment-13614875 ] Leif Hedstrom commented on TS-1767: --- Yeah, I played with this, I think when pristine host headers is enabled, we generate the wrong URLs in the cache inspector. > 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/ instead of > http://incoming/ > 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
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[
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://:/cache/ http://{cache}
Then I go to http://:/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://:/cache/lookup_url?url=http://origin/static/1.jpg. If
I change this url to
http://:/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/ instead of
> http://incoming/
> 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
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614700#comment-13614700 ] James Peach commented on TS-1767: - I don't really understand what you mean by "using the cache regex lookup" ... could you please explain like I'm 5? > 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/ instead of > http://incoming/ > 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
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609521#comment-13609521 ] Scott Harris commented on TS-1767: -- thanks for the suggestion, which works, but I have some sites that require the original host header to be passed through. > 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/ instead of > http://incoming/ > 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
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608616#comment-13608616 ] weijin commented on TS-1767: traffic_line -s proxy.config.url_remap.pristine_host_hdr -v 0 > 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/ instead of > http://incoming/ > 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
