These are comments copied from ap_cache_check_freshness()
line 163 cache_util.c:
----------------------
* - RFC2616 14.9.4 End to end reload, Cache-Control: no-cache. no-cache in
* either the request or the cached response means that we must
* revalidate the request unconditionally, overriding any expiration
* mechanism. It's equivalent to max-age=0,must-revalidate.
*
* - RFC2616 14.32 Pragma: no-cache This is treated the same as
* Cache-Control: no-cache.
----------------------
RFC2616 14.9.4:
_End-to-end reload_
The request includes a "no-cache" cache-control directive or, for compatibility with HTTP/1.0 clients,
"Pragma: no-cache". Field names MUST NOT be included with the no-cache directive in a request. The
server MUST NOT use a cached copy when responding to such a request.
1- Cache-Control: no-cache, I don't thing the no-cache case is taking care of in ap_cache_check_freshness().
2- _*Please comment*_: I might be wrong, but this is the way I think it should be done:
+1 I don't think it should be removed either. (BTW.. it wouldn't remove it completly from the webserver anyway.. as mem_cache stores the details in a process specific manner)
