https://issues.apache.org/bugzilla/show_bug.cgi?id=44696
rahul <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #22429|0 |1
is obsolete| |
--- Comment #3 from rahul <[EMAIL PROTECTED]> 2008-08-12 10:47:43 PST ---
Created an attachment (id=22433)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=22433)
patch to allow multiple passes
Thanks for pointing these out,
for the first one, I have modified the patch to look for APR_BUCKET_EOS before
commiting the headers. (at both points)
I do not understand the second issue,
if we have a fresh entitiy 1:head/url 1:body/url in our cache,
and Request A comes in with max-age = 0,
as it proceeds, the body gets written first, so we now have 1:head/url
2:body/url
Now assuming that at this point Request B comes in, and reads the headers
1:head/url but since it does not have max-age=0, it decides it can make do
with the current body, but the body is 2:body/url
However, there is no harm in serving a newer response? we only have a problem
with serving stale content, and 2:body/url is not stale.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
