![shared cache vs private cache shared cache vs private cache](https://docs.oracle.com/database/121/CNCPT/img/GUID-B71BA462-E5D5-4AB5-90BE-6E7668469CF2-default.gif)
- #Shared cache vs private cache how to
- #Shared cache vs private cache update
- #Shared cache vs private cache code
The response is then sent to the client who initiated the request.Īt this point, Cloudflare’s cache logic examines the HTTP response received from your origin server. If the resource is not present in the cache, Cloudflare requests the resource from your origin web server to fill the cache. In the response, Cloudflare first examines its caches in multiple network locations for content. If the content is stale in Cloudflare’s cache, Cloudflare attempts to revalidate the content with the origin before serving the response to the client. If the request matches an extension on this list, Cloudflare serves the resource from cache if it is present. When a user sends an HTTP request, the user’s request URL is matched against a list of cacheable file extensions.
![shared cache vs private cache shared cache vs private cache](https://image.slidesharecdn.com/sharepoint2013sdistributedcacheservice6-150904120634-lva1-app6892/95/share-point-2013s-distributed-cache-service-60-1-3-638.jpg)
#Shared cache vs private cache how to
Warning header field 3.3, 4.3.4, 4.3.5, 5.5, 7.3, AĪuthors' Addresses Roy T.Set Cache-Control headers to tell Cloudflare how to handle content from the origin.Transformation Applied (warn-text) 5.5.6, 7.2.2.proxy-revalidate (cache directive) 5.2.2.7.only-if-cached (cache directive) 5.2.1.7.must-revalidate (cache directive) 5.2.2.1.Miscellaneous Warning (warn-text) 5.5.5, 7.2.2.Miscellaneous Persistent Warning (warn-text) 5.5.7, 7.2.2.Cache-Control header field 3, 5.2, 7.3, A.If the new response does not include any form of validator (such as in the case where a client generates an If-Modified-Since request from a source other than the Last-Modified response header field), and there is only one stored response, and that stored response also lacks a validator, then that stored response is selected for update.If the new response contains a weak validator and that validator corresponds to one of the cache's stored responses, then the most recent of those matching stored responses is selected for update.
#Shared cache vs private cache update
If none of the stored responses contain the same strong validator, then the cache MUST NOT use the new response to update any stored responses. All of the stored responses with the same strong validator are selected.
![shared cache vs private cache shared cache vs private cache](https://www.alachisoft.com/ncache/images/ncache-azure-virtual-machine.jpg)
contains a public response directive (see Section 5.2.2.5).
#Shared cache vs private cache code
has a status code that is defined as cacheable by default (see Section 4.2.2), or.contains a Cache Control Extension (see Section 5.2.3) that allows it to be cached, or.contains a s-maxage response directive (see Section 5.2.2.9) and the cache is shared, or.contains a max-age response directive (see Section 5.2.2.8), or.contains an Expires header field (see Section 5.3), or.the Authorization header field (see Section 4.2 of ) does not appear in the request, if the cache is shared, unless the response explicitly allows it (see Section 3.2), and.the "private" response directive (see Section 5.2.2.6) does not appear in the response, if the cache is shared, and.the "no-store" cache directive (see Section 5.2) does not appear in request or response header fields, and.the response status code is understood by the cache, and.The request method is understood by the cache and defined as being cacheable, and.A cache MUST NOT store a response to any request, unless: