Hi all, I am trying to understand the apache documentation regarding cacheable content.
>From the documenation ( http://httpd.apache.org/docs/2.2/caching.html ): --------------------- Begin Apache 2.2 DOCUMENTATION ----------------------- What Can be Cached? mod_cache caching on the other hand is more complex. When serving a request, if it has not been cached previously, the caching module will determine if the content is cacheable. The conditions for determining cachability of a response are; 4. If the request contains an "Authorization:" header, the response will not be cached. 5. If the response contains an "Authorization:" header, it must also contain an "s-maxage", "must-revalidate" or "public" option in the "Cache-Control:" header. --------------------- End Apache 2.2 DOCUMENTATION ----------------------- Two questions regarding above 1) Is there actually a flag and/or a trick i can use so that a "response" from a request with a authorization header can actually be cached ? 2) When and why would ever a response actually contain a "authorization" header ? Thank you -seymen --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
