Source: https://trac.ietf.org/trac/httpbis/browser/draft-ietf-httpbis/latest/p5-range.html?annotate=blame&rev=1734
Timestamp: 2019-09-16 16:20:27
Document Index: 702825635

Matched Legal Cases: ['art1', 'art1', 'art 1', 'art1', 'art2', 'art2', 'art 2', 'art2', 'art2', 'art2', 'art 2', 'art2']

source: draft-ietf-httpbis/latest/p5-range.html @ 1734
Last change on this file since 1734 was 1734, checked in by julian.reschke@…, 7 years ago
Work-in-progress: hyperlink status codes definitions (P4)
<p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>:
<a href="#core.rules" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
stored responses are <a href="#status.206" class="smpl">206</a> responses, then the stored response with the most header fields is used as the source of header fields for the combined response,
except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from Content-Range, to replace all instances of the corresponding
is true. It does not affect the <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response returned if the conditional is false.
<p id="rfc.section.B.p.1">Clarify that it is not ok to use a weak validator in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)