Source: https://trac.ietf.org/trac/httpbis/browser/draft-ietf-httpbis/20/draft-ietf-httpbis-p6-cache-20.xml?rev=1807
Timestamp: 2020-02-29 00:33:33
Document Index: 308023813

Matched Legal Cases: ['art1', 'art2', 'art2', 'art2', 'art2', 'art2', 'art 5', 'art 7']

draft-ietf-httpbis-p6-cache-20.xml in draft-ietf-httpbis/20 – Hypertext Transfer Protocol Wiki
source: draft-ietf-httpbis/20/draft-ietf-httpbis-p6-cache-20.xml @ 1807
<rfc category="std" docName="draft-ietf-httpbis-p6-cache-20" ipr="pre5378Trust200902" obsoletes="2616">
<date month="July" year="2012" day="16"/>
is being constrained by the requirement. See Section 2 of <xref target="Part1"/> for definitions
In addition to the prose requirements placed upon them, senders MUST NOT
role. If a received protocol element is processed, the recipient MUST be
Location header field doesn't parse according to the ABNF,
(Section 2.1.1 of <xref target="Part2"/>) to the origin server; i.e., a cache is not allowed to
(including the following in Section 4 of <xref target="Part2"/>: 200 (OK),
operations. See Section 9.10 of <xref target="Part2"/> for the definition of the Date header
that has a <xref target="header.vary" format="none">Vary</xref> header field (<xref target="header.vary"/>),
A <xref target="header.vary" format="none">Vary</xref> header field-value of "*" always fails to match, and
Because unsafe request methods (Section 2.1.1 of <xref target="Part2"/>) such as PUT, POST or DELETE
Section 5.1 of <xref target="Part2"/>; a sender MUST use the rfc1123-date format.
response can be used to satisfy a given request; see <xref target="caching.negotiated.responses"/>.
<seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-20"/>
<seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-20"/>
<seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-20"/>
<title>HTTP/1.1, part 5: Range Requests</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-20"/>
<title>HTTP/1.1, part 7: Authentication</title>
Remove requirement to consider Content-Location in successful
Do not mention RFC 2047 encoding and multiple languages in <xref target="header.warning" format="none">Warning</xref>