There's probably several ways of doing this (such as, disabling
negative_caching etc), but, the most reliable way is to use header_rewrite to
turn off http.cache on a non-200 response.
Below's a sample config (I didn't test it myself, so, it may need some
twiddling around):
% cat plugin.config
header_rewrite.so negative_caching.config
% cat negative_caching.config
cond %{READ_RESPONSE_HDR_HOOK} [AND]
cond %{STATUS} >=400
set-config proxy.config.http.cache.http 0 [L]
Thanks,
Sudheer
On Wednesday, April 6, 2016 3:53 PM, "amit.sharm...@cognizant.com"
<amit.sharm...@cognizant.com> wrote:
Hi Team,
Need inputs from anyone who knows how to ask Trafficserver only to have
response status 200/ok data in the cache. I want to stop trafficserver to cache
404 status responses which sometimes makes the app malfunction until I don't go
manually in the cache and remove that forcing Trafficserver to re-cache the
file.
Thanks,
Amit
This e-mail and any files transmitted with it are for the sole use of the
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient(s), please reply to the sender and
destroy all copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email,
and/or any action taken in reliance on the contents of this e-mail is strictly
prohibited and may be unlawful. Where permitted by applicable law, this e-mail
and other e-mail communications sent to and from Cognizant e-mail addresses may
be monitored.
