httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 43826] Standards violation: POST does not invalidate the cache
Date Thu, 21 Aug 2008 12:10:07 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=43826


rahul <rahul@sun.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22459|0                           |1
        is obsolete|                            |




--- Comment #9 from rahul <rahul@sun.com>  2008-08-21 05:10:07 PST ---
Created an attachment (id=22467)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22467)
move cache_remove_url to output filter

Two parts to the patch, The first part is same as your logic,
but I thought this was a little more clearer, and moves auth check before
initialization of context.

The second part (I am not sure this is right since it is not stated in RFC) is
that we check if the PUT/POST/DELETE request was valid before removing the
cache entry. The reason that if a method was disallowed in the current URL,
then
it is probably not nice to let it have any effect on the cache of that entity.

Both parts are not really necessary, and your patch works fine,
(I have verified it, and could find no fault with its logic)
but I thought it might be nicer this way.


-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message