Received: (qmail 45708 invoked by uid 501); 5 Jul 2001 23:56:19 -0000 Message-Id: <20010705235619.45707.qmail@apache.org> Date: 5 Jul 2001 23:56:19 -0000 From: Brian Davison Reply-To: davison@cs.rutgers.edu To: submit@bugz.apache.org Subject: Apache will sometimes return a cached copy of an uncacheable object. X-Send-Pr-Version: 3.110 >Number: 7986 >Category: mod_proxy >Synopsis: Apache will sometimes return a cached copy of an uncacheable object. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Jul 05 17:00:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: davison@cs.rutgers.edu >Release: 1.3.14 >Organization: apache >Environment: RedHat 7 -- Linux miss.rutgers.edu 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT 2000 i686 unknown Standard install of apache-1.3.14-3.i386.rpm >Description: A description with examples, sample code can be found at: http://www.cs.rutgers.edu/~davison/error/ I'm not sure of the severity of this bug, except probably for high-volume reverse proxy caching with uncacheable resources. >How-To-Repeat: Multiple connections need to request the same file (probably at very close to the same time). >Fix: Haven't yet looked into the code. My wild guess is that apache allows the serving of objects in memory before they have been checked for cacheability. >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]