httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 44696] mod_cache sometimes serves old content despite having fetched new content
Date Tue, 12 Aug 2008 11:36:14 GMT

Ruediger Pluem <> changed:

           What    |Removed                     |Added
             Status|NEW                         |NEEDINFO

--- Comment #2 from Ruediger Pluem <>  2008-08-12 04:36:12 PST ---
The attached patch does not fix all cases:

1. store_body is no atomic operation. The content of the entity may be split
   across several brigades. So the race would be only fixed if the headers
   would be stored *after* a brigade containing an EOS bucket was passed
   to store_body. Keep in mind that store_body is called at 2 different
   in the CACHE_SAVE filter: One is used during the first pass of the filter
   the other one is used during the following passes. But it is not guaranteed 
   that more than one pass ever happens (e.g. if the first brigade already 
   contains the EOS bucket).

2. There is still a second race: Lets assume the entity is still fresh if a 
   request does not contain additional conditions. Now we have a request that
   requests a fresh response e.g. via max-age=0. Even if the patch works as
   there is the possibility that a second client got the old headers decides
   the entity is fresh enough for him and then tries to fetch the body which
   is now the new one.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message