[jira] [Comment Edited] (TS-2176) TSHttpTxnCacheLookupSkip doesn't work

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761180#comment-13761180 ] 

Leif Hedstrom edited comment on TS-2176 at 9/8/13 2:53 AM:
-----------------------------------------------------------

Turning off the cache entirely (early in the state machine) is actually the most efficient way of doing this. It avoids a potential cache lookup entirely, *and* subsequent locking of cache objects. So if you know a request should never be cached, do what James does. :) Maybe this is a common enough case that it would make sense to have its own API (TSHttpCacheEnabledSet(0|1);  ?
                
      was (Author: zwoop):
    Turning off the cache entirely (early in the state machine) is actually the most efficient way of doing this. It avoids a potential cache lookup entirely, *and* subsequent locking of cache objects. So if you know a request should never be cached, do what James does. :)
                  
> TSHttpTxnCacheLookupSkip doesn't work
> -------------------------------------
>
>                 Key: TS-2176
>                 URL: https://issues.apache.org/jira/browse/TS-2176
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>            Reporter: Corey Cossentino
>            Assignee: James Peach
>             Fix For: 4.1.0
>
>         Attachments: ts2176_api_skip_cache_lookup.patch
>
>
> When {{is_request_cache_lookupable}} reads the value of {{api_skip_cache_lookup}} it also resets the value to false. 
> Since the function is called from {{HandleRequest}}, the flag set by the API call will be ignored by {{DecideCacheLookup}}.

--
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