3/21/2023 0 Comments Using filecapsule deluxeThis document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. Received public review and has been approved for publication by the It represents the consensus of the IETF community. ![]() ![]() Internet Engineering Steering Group (IESG). Internet Standards is available in Section 2 of RFC 5741. ![]() Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atįielding, et al. Standards Track Ĭopyright (c) 2014 IETF Trust and the persons identified as the Shared cache vs private cache how to# The Trust Legal Provisions and are provided without warranty as Include Simplified BSD License text as described in Section 4.e of Shared cache vs private cache code#Ĭode Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal Material may not have granted the IETF Trust the right to allow The person(s) controlling the copyright in some of this This document may contain material from IETF Documents or IETFĬontributions published or made publicly available before Novemberġ0, 2008. Without obtaining an adequate license from the person(s) controlling Modifications of such material outside the IETF Standards Process. Not be created outside the IETF Standards Process, except to format Outside the IETF Standards Process, and derivative works of it may The copyright in such materials, this document may not be modified Shared cache vs private cache license# It for publication as an RFC or to translate it into languages otherġ. Storing Responses to Authenticated Requests. Freshening Stored Responses upon Validation. Warning: 299 - "Miscellaneous Persistent Warning". HTTP is typically used for distributed information systems, where Considerations for New Cache Control Directives. Thisĭocument defines aspects of HTTP/1.1 related to caching and reusingĪn HTTP cache is a local store of response messages and the subsystem Performance can be improved by the use of response caches. Used by a server that is acting as a tunnel.Ī shared cache is a cache that stores responses to be reused by more AĬache stores cacheable responses in order to reduce the response timeĪnd network bandwidth consumption on future, equivalent requests.Īny client or server MAY employ a cache, though a cache cannot be That controls storage, retrieval, and deletion of messages in it. (checking with the origin server to see if the cached response Section 4.2, if the response can be reused without "validation" A stored response is considered "fresh", as defined in Performance by reusing a prior response message to satisfy a current The goal of caching in HTTP/1.1 is to significantly improve A private cache, in contrast, isĭedicated to a single user often, they are deployed as a component Than one user shared caches are usually (but not always) deployed asĪ part of an intermediary. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", When a cached response is not fresh, it might still be reusable if itĬan be freshened by validation ( Section 4.3) or if the origin is Reduce both latency and network overhead each time it is reused. Lists using a '#' operator (similar to how the '*' operator indicates, that allows for compact definition of comma-separated Notation of with a list extension, defined in Section 7 of This specification uses the Augmented Backus-Naur Form (ABNF) Ĭonformance criteria and considerations regarding error handling are "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in. ![]() Appendix C shows the collected grammar with all list Appendix B describes rules imported from otherĭocuments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |