![]() Redirects, negative results (e.g., 404 (Not Found)), Request: i.e., a 200 (OK) response to a GET request, whichĬontains a representation of the target resource Most commonly, caches store the successful result of a retrieval Thereby "double keying" the cache to avoid some privacy risks (see Section 7.2). ¶Ĭaches might incorporate additional material into the cache key.įor example, user agent caches might include the referring site's identity, Response header field, as per Section 4.1. Into the cache key as well, using information in the Vary Caches differentiate these responsesīy incorporating some of the original request's header fields HTTP caches in common use today only cache GET responses and therefore onlyĪ cache might store multiple responses for a request target that is URI used to retrieve the stored response the method determines under whichĬircumstances that response can be used to satisfy a subsequent request. Is composed from, at a minimum, the request method and target The "cache key" is the information a cache uses to choose a response and Reusing a stored response inappropriately, rather than mandating thatĬaches always store and reuse particular responses. On preventing a cache from either storing a non-reusable response or Therefore, HTTP cache requirements are focused Is the default behavior when no requirement or local configuration ¶Īlthough caching is an entirely OPTIONAL feature of HTTP, it can beĪssumed that reusing a cached response is desirable and that such reuse While reducing the transmission of information already held in theįor the general terminology and core concepts of HTTP. Proper cache operation preserves the semantics of HTTP transfers Works of it may not be created outside the IETF Standards Process,Įxcept to format it for publication as an RFC or to translate it Without obtaining an adequate license from the person(s)Ĭontrolling the copyright in such materials, this document may notīe modified outside the IETF Standards Process, and derivative Modifications of such material outside the IETF Standards Process. 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. Warranty as described in the Revised BSD License. Section 4.e of the Trust Legal Provisions and are provided without Code Components extracted from thisĭocument must include Revised BSD License text as described in ![]() Please review these documentsĬarefully, as they describe your rights and restrictions with This document is subject to BCP 78 and the IETF Trust's Legal Copyright (c) 2022 IETF Trust and the persons identified as the ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |