Ignore:
Timestamp:
Dec 21, 2007, 4:30:59 PM (12 years ago)
Author:
fielding@…
Message:

Regenerate HTML after the following changes applied to XML drafts:

Resolve #1: HTTP Version should be case sensitive
Resolve #2: 'unsafe' characters
Resolve #3: Chunk Size Definition
Resolve #4: Message Length
Resolve #5: Via is a MUST
Resolve #6: Fragments allowed in Location
Resolve #8: Media type registrations, by updating to RFC 4288
Resolve #8: Media type registrations, by updating to RFC 4288
Resolve #9: Trailer
Resolve #11: URI includes query
Resolve #12: Invalidation after Update or Delete
Resolve #17: Revise description of the POST method
Resolve #18: Cache validators in 206 responses
Resolve #49: Connection header text
Resolve #14: Clarification regarding quoting of charset values
Resolve #47: inconsistency in date format explanation
Resolve #48: Date reference typo
Resolve #48: remove unnecessary reference to RFC1123

for consistency with draft-lafon

Resolve #16: Remove 'identity' token references
Resolve #15: No close on 1xx responses
(editorial) fix typo of varriant
Resolve #10: Safe Methods vs Redirection
Resolve #45: RFC977 reference
Resolve #42: RFC2606 compliance
Resolve #46: references to RFC1700

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r62 r92  
    993993         <li>Proxy-Authorization</li>
    994994         <li>TE</li>
    995          <li>Trailers</li>
     995         <li>Trailer</li>
    996996         <li>Transfer-Encoding</li>
    997997         <li>Upgrade</li>
    998998      </ul>
    999999      <p id="rfc.section.2.5.1.p.3">All other headers defined by HTTP/1.1 are end-to-end headers.</p>
    1000       <p id="rfc.section.2.5.1.p.4">Other hop-by-hop headers <em class="bcp14">MUST</em> be listed in a Connection header, (<a href="p1-messaging.html#header.connection" title="Connection">Section 8.1</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to be introduced into HTTP/1.1 (or later).
     1000      <p id="rfc.section.2.5.1.p.4">Other hop-by-hop headers <em class="bcp14">MUST</em> be listed in a Connection header (<a href="p1-messaging.html#header.connection" title="Connection">Section 8.1</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    10011001      </p>
    10021002      <h3 id="rfc.section.2.5.2"><a href="#rfc.section.2.5.2">2.5.2</a>&nbsp;<a id="non-modifiable.headers" href="#non-modifiable.headers">Non-modifiable Headers</a></h3>
     
    11431143         <li>POST</li>
    11441144      </ul>
    1145       <p id="rfc.section.2.10.p.5">In order to prevent denial of service attacks, an invalidation based on the URI in a Location or Content-Location header <em class="bcp14">MUST</em> only be performed if the host part is the same as in the Request-URI.
     1145      <p id="rfc.section.2.10.p.5">An invalidation based on the URI in a Location or Content-Location header <em class="bcp14">MUST NOT</em> be performed if the host part of that URI differs from the host part in the Request-URI. This helps prevent denial of service
     1146         attacks.
    11461147      </p>
    11471148      <p id="rfc.section.2.10.p.6">A cache that passes through requests for methods it does not understand <em class="bcp14">SHOULD</em> invalidate any entities referred to by the Request-URI.
Note: See TracChangeset for help on using the changeset viewer.