We have the stale-while-revalidate plugin in place and have noticed some
behavior that seems suboptimal. While cache is fresh, everything works great.
The first page hit after our 300sec s-maxage has passed comes back with
“Warning: 110 Response is stale” as expected. However, it appears to b
lement
>>>stale-while-revalidate, we¹d need to make changes in the cache such
>>>that it does not update the dir entries etc. until the ³new² version is
>>>available to be served. Alan?
>>>
>>> ‹ leif
>>>
>>>>
>>>> Kit
&
Does your proxy.config.admin.user_id in records.config match the owner of
your ATS files? I recently had those out of sync and traffic_cop would
start but not traffic_manager or traffic_server. I seem to remember it
throwing some relevant errors in /var/log/messages.
.: Jared
On 10/28/14, 7:16
