For evicting the cached version and forcing the request to be sent to
origin, he could do like what plugin
/plugins/experimental/regex_revalidate/ does, that is, on event
TS_EVENT_HTTP_CACHE_LOOKUP_COMPLETE, do TSHttpTxnCacheLookupStatusSet(txn,
TS_CACHE_LOOKUP_HIT_STALE);
Acácio Centeno
Software
Hi Alan,
Thomas¹s requirement has two parts:
- Requests to URI /a are cached
- If condition x matched, requests to /a must bypass the cache and served
>From the origin without putting the response into the cache
>From what I understand, essentially, the use case is to force certain
client reque
Monday, October 6, 2014, 4:51:12 AM, you wrote:
> - Requests to URI /a are cached
> - If condition x matched, requests to /a must bypass the cache and served
> from
> the origin without putting the response into the cache
Look TSHttpTxnServerRespNoStoreSet().
To simple ... thank you!
Am Montag, 6. Oktober 2014, 14:29:04 schrieb Sudheer Vinukonda:
> You may want to checkout the API TSHttpTxnConfigIntSet that allows
> overriding the setting "proxy.config.http.cache.http".
>
> For example:
>
> TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0);
>
You may want to checkout the API TSHttpTxnConfigIntSet that allows
overriding the setting "proxy.config.http.cache.http".
For example:
TSHttpTxnConfigIntSet(txn, TS_CONFIG_HTTP_CACHE_HTTP, 0);
Thanks,
Sudheer
On 10/6/14, 2:51 AM, "Thomas Berger" wrote:
>Hi all,
>
>for one of our project
Hi all,
for one of our projects, we need to bypass the cache under specific conditions.
I found no way right now to set a request to non-cacheable in the plugin API
documentation.
`TSHttpTxnReqCacheableSet` does only force a request to be cachable.
Is there any way to enforce the following:
