[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls

["Christoph Keller (JIRA)" <ji...@apache.org>]

    [ 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 80000 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/<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.3.4#6332)