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 Wed, 20 Aug 2008 20:16:29 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=43826





--- Comment #7 from Ruediger Pluem <rpluem@apache.org>  2008-08-20 13:16:29 PST ---
(In reply to comment #6)
> Created an attachment (id=22459)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22459) [details]
> let PUT POST DELETE invalidate the cache
> 
> Check for PUT|POST|DELETE and if we have a cache entry matching the request,
> remove that entry.
> 

I think the patch misses some cases that will be caught by the patch I will add
in a minute.

1. Even if cache_select returns DECLINED we can have a caches version of this
   resource. It is possible that this cached version looks stale at the *first*
   glance. A conditional request on the backend will show if this is true or
   not. So we must remove the cache entry regardless of the result of 
   cache_select.

2. It is perfectly valid that a POST, DELETE or PUT request on a resource
requires
   authorization whereas a GET request does not. So must avoid the shortcut
that
   every request with an Authorization header present in the request gets
   declined.


-- 
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