Hi Everyone,
Is there any way to configure Magnolia's cache to never cache a 401 response?
We have a site running Magnolia 4.3.6 CE where this is happening a lot and the
only way to resolve it is to re-activate the pages. I'm getting this in the
log:
Caching response 401 for DefaultCacheKey{uri='/foo/bar.html',
serverName='newdemo.portfolio.projectfoundry.org', locale='en', params={}}
I think the problem is caused by the public side having some pages that are
protected and others that are not. The anonymous role has access to view
everything but perhaps some of our other logged in user roles do not have
access to view everything, resulting in the 401 response ending up in the
cache. I am going to track this down but it would be great if we could just
configure Magnolia to not cache a 401 response.
Tom
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
