It seems the page (or image in this case) was cached with the 404. Magnolia 
assumes that if cacheable resource is not available in the public instance it 
will not be available until the next activation so the 404 is cached and served 
from the cache later. The question is why it could not be retrieved originally 
and ended with 404 in the first place.
Does this happen always for the same image or is it more less random? Does the 
problem occur only for binary resources?
HTH,
Jan

On Jun 10, 2010, at 2:41 PM, rainer wrote:

> 
> 
> Hi list,
> 
> since a couple of days we see the following problem re-occur in a magnolia
> live system: 
> 
> EE 4.1.1
> 
> A document that is being requested from a public server: "/dms/image.JPG"
> serves a HTTP 404. If i request it that way: "/dms/image.JPG?abc=def" and
> the magnolia cache is not being used - i get the image with HTTP 200.
> 
> If the magnolia cache is flushed by activating any page - the problem
> disappears.
> 
> Did anyone ever experience sth. like that?
> 
> 
> 
> kind regards
> rainer
> -- 
> View this message in context: 
> http://old.nabble.com/Magnolia-cache-delivers-404---but-page-is-present-tp28842539p28842539.html
> Sent from the Magnolia - User mailing list archive at Nabble.com.
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------

-  
Best regards,

Jan Haderka, PhD.
Magnolia International Ltd.

http://www.magnolia-cms.com

You should join us at Magnolia Conference 2010: 
http://www.magnolia-cms.com/conference

http://twitter.com/magnolia_cms
http://facebook.com/Magnolia

--------------------------------------

Magnolia®  - Simple Open-Source Content Management





----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to