Ignore:
Timestamp:
Dec 21, 2007, 12:21:13 AM (12 years ago)
Author:
fielding@…
Message:

generate diffs for submitted drafts 00

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/diffs/draft-ietf-httpbis-p1-messaging-00-from-rfc2616-symrefs.diff.html

    r61 r65  
    11<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    22<!-- Generated by rfcdiff 1.34: rfcdiff  -->
     3<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
     4<!-- System: Darwin kiwi.local 8.11.0 Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh powerpc -->
     5<!-- Using awk: /usr/local/bin/gawk: GNU Awk 3.1.6 -->
     6<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 -->
     7<!-- Using wdiff: /usr/local/bin/wdiff: wdiff (Free wdiff) 0.5g -->
    38<html>
    49<head>
     
    3843      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    3944      <tr><td><a name="diff0001" /></td></tr>
    40       <tr><td class="lineno" valign="top"></td><td class="lblock">Network Working Group                                   <span class="delete">     R. Fielding</span></td><td> </td><td class="rblock">Network Working Group                                   <span class="insert">R. Fielding, Ed.</span></td><td class="lineno" valign="top"></td></tr>
    41       <tr><td class="lineno" valign="top"></td><td class="lblock">Internet-Draft                                              <span class="delete">   UC Irvin</span>e</td><td> </td><td class="rblock">Internet-Draft                                              <span class="insert">Day Softwar</span>e</td><td class="lineno" valign="top"></td></tr>
    42       <tr><td class="lineno" valign="top"></td><td class="lblock">Obsoletes: 2068<span class="delete"> (if approved)</span>                                  J. Gettys</td><td> </td><td class="rblock">Obsoletes: 2068<span class="insert">, 2616        </span>                                  J. Gettys</td><td class="lineno" valign="top"></td></tr>
    43       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status: Standards Track                              Compaq/W3C</span></td><td> </td><td class="rblock"><span class="insert">(if approved)                                       One Laptop per Child</span></td><td class="lineno" valign="top"></td></tr>
    44       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: December 3, 1999       </span>                                J. Mogul</td><td> </td><td class="rblock"><span class="insert">Intended status: Standards Track</span>                                J. Mogul</td><td class="lineno" valign="top"></td></tr>
    45       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                  Compaq</span></td><td> </td><td class="rblock"><span class="insert">Expires: June 20, 2008                                                HP</span></td><td class="lineno" valign="top"></td></tr>
     45      <tr><td class="lineno" valign="top"></td><td class="lblock">Network Working Group                                        R. <span class="delete">Fielding</span></td><td> </td><td class="rblock">Network Working Group                                   R. <span class="insert">Fielding, Ed.</span></td><td class="lineno" valign="top"></td></tr>
     46      <tr><td class="lineno" valign="top"></td><td class="lblock">Internet-Draft                                                 <span class="delete">UC Irvine</span></td><td> </td><td class="rblock">Internet-Draft                                              <span class="insert">Day Software</span></td><td class="lineno" valign="top"></td></tr>
     47      <tr><td class="lineno" valign="top"></td><td class="lblock">Obsoletes: <span class="delete">2068 (if approved)</span>                                  J. Gettys</td><td> </td><td class="rblock">Obsoletes: <span class="insert">2068, 2616</span>                                          J. Gettys</td><td class="lineno" valign="top"></td></tr>
     48      <tr><td class="lineno" valign="top"></td><td class="lblock">Intended status: Standards Track                              <span class="delete">Compaq/W3C</span></td><td> </td><td class="rblock"><span class="insert">(if approved)                                       One Laptop per Child</span></td><td class="lineno" valign="top"></td></tr>
     49      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: December 3, 1999</span>                                       J. Mogul</td><td> </td><td class="rblock">Intended status: Standards Track                                J. Mogul</td><td class="lineno" valign="top"></td></tr>
     50      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                  <span class="delete">Compaq</span></td><td> </td><td class="rblock"><span class="insert">Expires: June 22, 2008                                                HP</span></td><td class="lineno" valign="top"></td></tr>
    4651      <tr><td class="lineno" valign="top"></td><td class="left">                                                              H. Frystyk</td><td> </td><td class="right">                                                              H. Frystyk</td><td class="lineno" valign="top"></td></tr>
    4752      <tr><td><a name="diff0002" /></td></tr>
     
    5560      <tr><td class="lineno" valign="top"></td><td class="left">                                                                 W3C/MIT</td><td> </td><td class="right">                                                                 W3C/MIT</td><td class="lineno" valign="top"></td></tr>
    5661      <tr><td><a name="diff0004" /></td></tr>
    57       <tr><td class="lineno" valign="top"></td><td class="lblock">                <span class="delete">Hypertext Transfer Protocol -- HTTP/1.1</span></td><td> </td><td class="rblock">                <span class="insert">                                       December 18, 2007</span></td><td class="lineno" valign="top"></td></tr>
    58       <tr><td class="lineno" valign="top"></td><td class="lblock">                            <span class="delete">rfc2616-symrefs</span></td><td> </td><td class="rblock">                            <span class="insert">                                             </span></td><td class="lineno" valign="top"></td></tr>
     62      <tr><td class="lineno" valign="top"></td><td class="lblock">                <span class="delete">Hypertext Transfer Protocol -- HTTP/1.1</span></td><td> </td><td class="rblock">                                                       <span class="insert">December 20, 2007</span></td><td class="lineno" valign="top"></td></tr>
     63      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                            rfc2616-symrefs</span></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
    5964      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">        HTTP/1.1, part 1: URIs, Connections, and Message Parsing</span></td><td class="lineno" valign="top"></td></tr>
    6065      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                   draft-ietf-httpbis-p1-messaging-00</span></td><td class="lineno" valign="top"></td></tr>
     
    8287      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    8388      <tr><td><a name="diff0005" /></td></tr>
    84       <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">December 3, 1999</span>.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">June 20, 2008</span>.</td><td class="lineno" valign="top"></td></tr>
     89      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">December 3, 1999</span>.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">June 22, 2008</span>.</td><td class="lineno" valign="top"></td></tr>
    8590      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    8691      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
     
    9499      <tr><td class="lineno" valign="top"></td><td class="left">   protocol for distributed, collaborative, hypermedia information</td><td> </td><td class="right">   protocol for distributed, collaborative, hypermedia information</td><td class="lineno" valign="top"></td></tr>
    95100      <tr><td><a name="diff0007" /></td></tr>
    96       <tr><td class="lineno" valign="top"></td><td class="lblock">   systems.  <span class="delete">It is a generic, stateless, protocol which can be used for</span></td><td> </td><td class="rblock">   systems.  <span class="insert">HTTP has been in use by the World Wide Web global</span></td><td class="lineno" valign="top"></td></tr>
    97       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">many tasks beyond its use for hypertext, such as name servers and</span></td><td> </td><td class="rblock">   <span class="insert">information initiative since 1990.  This document is Part 1 of the</span></td><td class="lineno" valign="top"></td></tr>
    98       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">distributed object management systems, through extension of it</span>s</td><td> </td><td class="rblock">   <span class="insert">seven-part specification that defines the protocol referred to a</span>s</td><td class="lineno" valign="top"></td></tr>
    99       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">request methods, error codes and headers [RFC2324].  A feature of</span></td><td> </td><td class="rblock">   <span class="insert">"HTTP/1.1" and, taken together, obsoletes RFC 2616.  Part 1 provides</span></td><td class="lineno" valign="top"></td></tr>
    100       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">HTTP is the typing and negotiation of data representation, allowing</span></td><td> </td><td class="rblock">   <span class="insert">an overview of HTTP and its associated terminology, defines the</span></td><td class="lineno" valign="top"></td></tr>
    101       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">systems to be built independently of the data being transferred.</span></td><td> </td><td class="rblock">   <span class="insert">"http" and "https" Uniform Resource Identifier (URI) schemes, defines</span></td><td class="lineno" valign="top"></td></tr>
    102       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">                                                                      </span></td><td> </td><td class="rblock">   <span class="insert">the generic message syntax and parsing requirements for HTTP message</span></td><td class="lineno" valign="top"></td></tr>
    103       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">HTTP has been in use by the World-Wide Web global information</span></td><td> </td><td class="rblock">   <span class="insert">frames, and describes general security concerns for implementations.</span></td><td class="lineno" valign="top"></td></tr>
    104       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   initiative since 1990.  This specification defines the protocol</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    105       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   referred to as "HTTP/1.1", and is an update to RFC 2068 [RFC2068].</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     101      <tr><td class="lineno" valign="top"></td><td class="lblock">   systems.  <span class="delete">It is a generic, stateless, protocol which can be used for</span></td><td> </td><td class="rblock">   systems.  HTTP has been in use by the <span class="insert">World Wide</span> Web global</td><td class="lineno" valign="top"></td></tr>
     102      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   many tasks beyond its use for hypertext, such as name servers and</span></td><td> </td><td class="rblock">   information initiative since 1990.  This <span class="insert">document is Part 1 of the</span></td><td class="lineno" valign="top"></td></tr>
     103      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   distributed object management systems, through extension of its</span></td><td> </td><td class="rblock"><span class="insert">   seven-part</span> specification <span class="insert">that</span> defines the protocol referred to as</td><td class="lineno" valign="top"></td></tr>
     104      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request methods, error codes and headers [RFC2324].  A feature of</span></td><td> </td><td class="rblock">   <span class="insert">"HTTP/1.1" and, taken together, obsoletes</span> RFC <span class="insert">2616.  Part 1 provides</span></td><td class="lineno" valign="top"></td></tr>
     105      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP is the typing and negotiation of data representation, allowing</span></td><td> </td><td class="rblock"><span class="insert">   an overview of HTTP and its associated terminology, defines the</span></td><td class="lineno" valign="top"></td></tr>
     106      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   systems to be built independently of the data being transferred.</span></td><td> </td><td class="rblock"><span class="insert">   "http" and "https" Uniform Resource Identifier (URI) schemes, defines</span></td><td class="lineno" valign="top"></td></tr>
     107      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"><span class="insert">   the generic message syntax and parsing requirements for HTTP message</span></td><td class="lineno" valign="top"></td></tr>
     108      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP has been in use by the <span class="delete">World-Wide</span> Web global information</td><td> </td><td class="rblock"><span class="insert">   frames, and describes general security concerns for implementations.</span></td><td class="lineno" valign="top"></td></tr>
     109      <tr><td class="lineno" valign="top"></td><td class="lblock">   initiative since 1990.  This specification defines the protocol</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     110      <tr><td class="lineno" valign="top"></td><td class="lblock">   referred to as <span class="delete">"HTTP/1.1", and is an update to</span> RFC <span class="delete">2068 [RFC2068].</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    106111      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    107112      <tr><td class="lineno" valign="top"></td><td class="left">Editorial Note (To be removed by RFC Editor)</td><td> </td><td class="right">Editorial Note (To be removed by RFC Editor)</td><td class="lineno" valign="top"></td></tr>
     
    109114      <tr><td><a name="diff0008" /></td></tr>
    110115      <tr><td class="lineno" valign="top"></td><td class="lblock">   This version of the HTTP specification contains only <span class="delete">XML processing</span></td><td> </td><td class="rblock">   This version of the HTTP specification contains only <span class="insert">minimal</span></td><td class="lineno" valign="top"></td></tr>
    111       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">changes from [RFC2616] in internet-draft form for use in creating</span></td><td> </td><td class="rblock">   <span class="insert">editorial changes from [RFC2616] (abstract, introductory paragraph,</span></td><td class="lineno" valign="top"></td></tr>
    112       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">diffs.</span></td><td> </td><td class="rblock">   <span class="insert">and authors' addresses).  All other changes are due to partitioning</span></td><td class="lineno" valign="top"></td></tr>
    113       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the original into seven mostly independent parts.  The intent is for</span></td><td class="lineno" valign="top"></td></tr>
    114       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   readers of future drafts to able to use draft 00 as the basis for</span></td><td class="lineno" valign="top"></td></tr>
     116      <tr><td class="lineno" valign="top"></td><td class="lblock">   changes from [RFC2616] <span class="delete">in internet-draft form</span> for use in <span class="delete">creating</span></td><td> </td><td class="rblock"><span class="insert">   editorial</span> changes from [RFC2616] <span class="insert">(abstract, introductory paragraph,</span></td><td class="lineno" valign="top"></td></tr>
     117      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   diffs.</span></td><td> </td><td class="rblock"><span class="insert">   and authors' addresses).  All other changes are due to partitioning</span></td><td class="lineno" valign="top"></td></tr>
     118      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the original into seven mostly independent parts.  The intent is</span> for</td><td class="lineno" valign="top"></td></tr>
     119      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">readers of future drafts to able to</span> use <span class="insert">draft 00 as the basis for</span></td><td class="lineno" valign="top"></td></tr>
    115120      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   comparison when the WG makes later changes to the specification text.</span></td><td class="lineno" valign="top"></td></tr>
    116121      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   This draft will shortly be followed by draft 01 (containing the first</span></td><td class="lineno" valign="top"></td></tr>
    117122      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   round of changes that have already been agreed to on the mailing</span></td><td class="lineno" valign="top"></td></tr>
    118       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   list).  There is no point in reviewing this draft other than to</span></td><td class="lineno" valign="top"></td></tr>
     123      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   list).  There is no point</span> in <span class="insert">reviewing this draft other than to</span></td><td class="lineno" valign="top"></td></tr>
    119124      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   verify that the partitioning has been done correctly.  Roy T.</span></td><td class="lineno" valign="top"></td></tr>
    120125      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Fielding, Yves Lafon, and Julian Reschke will be the editors after</span></td><td class="lineno" valign="top"></td></tr>
    121126      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   draft 00 is submitted.</span></td><td class="lineno" valign="top"></td></tr>
    122       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                                                                         </span></td><td class="lineno" valign="top"></td></tr>
     127      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
    123128      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Discussion of this draft should take place on the HTTPBIS working</span></td><td class="lineno" valign="top"></td></tr>
    124129      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   group mailing list (ietf-http-wg@w3.org).  The current issues list is</span></td><td class="lineno" valign="top"></td></tr>
    125       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   at &lt;http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/&gt; and</span></td><td class="lineno" valign="top"></td></tr>
    126       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   related documents (including fancy diffs) can be found at</span></td><td class="lineno" valign="top"></td></tr>
     130      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   at &lt;http://www3.tools.ietf.org/wg/httpbis/trac/report/11&gt; and related</span></td><td class="lineno" valign="top"></td></tr>
     131      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   documents (including fancy diffs) can be found at</span></td><td class="lineno" valign="top"></td></tr>
    127132      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   &lt;http://www3.tools.ietf.org/wg/httpbis/&gt;.</span></td><td class="lineno" valign="top"></td></tr>
    128133      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    130135      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    131136      <tr><td><a name="diff0009" /></td></tr>
    132       <tr><td class="lineno" valign="top"></td><td class="lblock">   1.  Introduction <span class="delete"> . . . . . . . . . . . . . . . . . . . . . . . .   9</span></td><td> </td><td class="rblock">   1.  Introduction <span class="insert">. . . . . . . . . . . . . . . . . . . . . . . . .  5</span></td><td class="lineno" valign="top"></td></tr>
    133       <tr><td class="lineno" valign="top"></td><td class="lblock">     1.1.  <span class="delete"> Purpose  . . . . . . . . . . . . . . . . . . . . . . . .   9</span></td><td> </td><td class="rblock">     1.1.  <span class="insert">Purpose  . . . . . . . . . . . . . . . . . . . . . . . . .  5</span></td><td class="lineno" valign="top"></td></tr>
    134       <tr><td class="lineno" valign="top"></td><td class="lblock">     1.2.  <span class="delete"> Requirements . . . . . . . . . . . . . . . . . . . . . .   9</span></td><td> </td><td class="rblock">     1.2.  <span class="insert">Requirements . . . . . . . . . . . . . . . . . . . . . . .  6</span></td><td class="lineno" valign="top"></td></tr>
    135       <tr><td class="lineno" valign="top"></td><td class="lblock">     1.3.  <span class="delete"> Terminology  . . . . . . . . . . . . . . . . . . . . . .  10</span></td><td> </td><td class="rblock">     1.3.  <span class="insert">Terminology  . . . . . . . . . . . . . . . . . . . . . . .  6</span></td><td class="lineno" valign="top"></td></tr>
    136       <tr><td class="lineno" valign="top"></td><td class="lblock">     1.4.  <span class="delete"> Overall Operation  . . . . . . . . . . . . . . . . . . .  14</span></td><td> </td><td class="rblock">     1.4.  <span class="insert">Overall Operation  . . . . . . . . . . . . . . . . . . . .  9</span></td><td class="lineno" valign="top"></td></tr>
    137       <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  Notational Conventions and Generic Grammar <span class="delete"> . . . . . . . . .  16</span></td><td> </td><td class="rblock">   2.  Notational Conventions and Generic Grammar <span class="insert">. . . . . . . . . . 11</span></td><td class="lineno" valign="top"></td></tr>
    138       <tr><td class="lineno" valign="top"></td><td class="lblock">     2.1.  <span class="delete"> Augmented BNF  . . . . . . . . . . . . . . . . . . . . .  16</span></td><td> </td><td class="rblock">     2.1.  <span class="insert">Augmented BNF  . . . . . . . . . . . . . . . . . . . . . . 11</span></td><td class="lineno" valign="top"></td></tr>
    139       <tr><td class="lineno" valign="top"></td><td class="lblock">     2.2.  <span class="delete"> Basic Rules  . . . . . . . . . . . . . . . . . . . . . .  18</span></td><td> </td><td class="rblock">     2.2.  <span class="insert">Basic Rules  . . . . . . . . . . . . . . . . . . . . . . . 13</span></td><td class="lineno" valign="top"></td></tr>
    140       <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  Protocol Parameters <span class="delete">. . . . . . . . . . . . . . . . . . . . .  20</span></td><td> </td><td class="rblock">   3.  Protocol Parameters <span class="insert"> . . . . . . . . . . . . . . . . . . . . . 15</span></td><td class="lineno" valign="top"></td></tr>
    141       <tr><td class="lineno" valign="top"></td><td class="lblock">     3.1.  <span class="delete"> HTTP Version . . . . . . . . . . . . . . . . . . . . . .  20</span></td><td> </td><td class="rblock">     3.1.  <span class="insert">HTTP Version . . . . . . . . . . . . . . . . . . . . . . . 15</span></td><td class="lineno" valign="top"></td></tr>
    142       <tr><td class="lineno" valign="top"></td><td class="lblock">     3.2.  <span class="delete"> Uniform Resource Identifiers . . . . . . . . . . . . . .  21</span></td><td> </td><td class="rblock">     3.2.  <span class="insert">Uniform Resource Identifiers . . . . . . . . . . . . . . . 16</span></td><td class="lineno" valign="top"></td></tr>
    143       <tr><td class="lineno" valign="top"></td><td class="lblock">       3.2.1.  <span class="delete"> General Syntax . . . . . . . . . . . . . . . . . . .  21</span></td><td> </td><td class="rblock">       3.2.1.  <span class="insert">General Syntax . . . . . . . . . . . . . . . . . . . . 16</span></td><td class="lineno" valign="top"></td></tr>
    144       <tr><td class="lineno" valign="top"></td><td class="lblock">       3.2.2.  <span class="delete"> http URL . . . . . . . . . . . . . . . . . . . . . .  22</span></td><td> </td><td class="rblock">       3.2.2.  <span class="insert">http URL . . . . . . . . . . . . . . . . . . . . . . . 17</span></td><td class="lineno" valign="top"></td></tr>
    145       <tr><td class="lineno" valign="top"></td><td class="lblock">       3.2.3.  <span class="delete"> URI Comparison . . . . . . . . . . . . . . . . . . .  22</span></td><td> </td><td class="rblock">       3.2.3.  <span class="insert">URI Comparison . . . . . . . . . . . . . . . . . . . . 17</span></td><td class="lineno" valign="top"></td></tr>
    146       <tr><td class="lineno" valign="top"></td><td class="lblock">     3.3.  <span class="delete"> Date/Time Formats  . . . . . . . . . . . . . . . . . . .  23</span></td><td> </td><td class="rblock">     3.3.  <span class="insert">Date/Time Formats  . . . . . . . . . . . . . . . . . . . . 18</span></td><td class="lineno" valign="top"></td></tr>
    147       <tr><td class="lineno" valign="top"></td><td class="lblock">       3.3.1.  <span class="delete"> Full Date  . . . . . . . . . . . . . . . . . . . . .  23</span></td><td> </td><td class="rblock">       3.3.1.  <span class="insert">Full Date  . . . . . . . . . . . . . . . . . . . . . . 18</span></td><td class="lineno" valign="top"></td></tr>
    148       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  3.3.2.   Delta Seconds  . . . . . . . . . . . . . . . . . . .  24</span></td><td> </td><td class="rblock">     <span class="insert">3.4.  Transfer Codings . . . . . . . . . . . . . . . . . . . . . 19</span></td><td class="lineno" valign="top"></td></tr>
    149       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.4.   Character Sets . . . . . . . . . . . . . . . . . . . . .  24</span></td><td> </td><td class="rblock">     <span class="insert">  3.4.1.  Chunked Transfer Coding  . . . . . . . . . . . . . . . 20</span></td><td class="lineno" valign="top"></td></tr>
    150       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">    3.4.1.   Missing Charset  . . . . . . . . . . . . . . . . . .  25</span></td><td> </td><td class="rblock">   <span class="insert">4.  HTTP Message . . . . . . . . . . . . . . . . . . . . . . . . . 22</span></td><td class="lineno" valign="top"></td></tr>
    151       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.5.   Content Codings  . . . . . . . . . . . . . . . . . . . .  25</span></td><td> </td><td class="rblock">     <span class="insert">4.1.  Message Types  . . . . . . . . . . . . . . . . . . . . . . 22</span></td><td class="lineno" valign="top"></td></tr>
    152       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.6.   Transfer Codings . . . . . . . . . . . . . . . . . . . .  27</span></td><td> </td><td class="rblock">     <span class="insert">4.2.  Message Headers  . . . . . . . . . . . . . . . . . . . . . 23</span></td><td class="lineno" valign="top"></td></tr>
    153       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  3.6.1.   Chunked Transfer Coding  . . . . . . . . . . . . . .  28</span></td><td> </td><td class="rblock">     <span class="insert">4.3.  Message Body . . . . . . . . . . . . . . . . . . . . . . . 24</span></td><td class="lineno" valign="top"></td></tr>
    154       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.7.   Media Types  . . . . . . . . . . . . . . . . . . . . . .  29</span></td><td> </td><td class="rblock">     <span class="insert">4.4.  Message Length . . . . . . . . . . . . . . . . . . . . . . 25</span></td><td class="lineno" valign="top"></td></tr>
    155       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  3.7.1.   Canonicalization and Text Defaults . . . . . . . . .  30</span></td><td> </td><td class="rblock">     <span class="insert">4.5.  General Header Fields  . . . . . . . . . . . . . . . . . . 26</span></td><td class="lineno" valign="top"></td></tr>
    156       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">    3.7.2.   Multipart Types  . . . . . . . . . . . . . . . . . .  30</span></td><td> </td><td class="rblock">   <span class="insert">5.  Request  . . . . . . . . . . . . . . . . . . . . . . . . . . . 26</span></td><td class="lineno" valign="top"></td></tr>
    157       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.8.   Product Tokens . . . . . . . . . . . . . . . . . . . . .  31</span></td><td> </td><td class="rblock">     <span class="insert">5.1.  Request-Line . . . . . . . . . . . . . . . . . . . . . . . 27</span></td><td class="lineno" valign="top"></td></tr>
    158       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.9.   Quality Values . . . . . . . . . . . . . . . . . . . . .  32</span></td><td> </td><td class="rblock">     <span class="insert">  5.1.1.  Method . . . . . . . . . . . . . . . . . . . . . . . . 27</span></td><td class="lineno" valign="top"></td></tr>
    159       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.10.  Language Tags  . . . . . . . . . . . . . . . . . . . . .  32</span></td><td> </td><td class="rblock">     <span class="insert">  5.1.2.  Request-URI  . . . . . . . . . . . . . . . . . . . . . 27</span></td><td class="lineno" valign="top"></td></tr>
    160       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">3.11.  Entity Tags  . . . . . . . . . . . . . . . . . . . . . .  33</span></td><td> </td><td class="rblock">     <span class="insert">5.2.  The Resource Identified by a Request . . . . . . . . . . . 28</span></td><td class="lineno" valign="top"></td></tr>
    161       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">  3.12.  Range Units  . . . . . . . . . . . . . . . . . . . . . .  33</span></td><td> </td><td class="rblock">   <span class="insert">6.  Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 29</span></td><td class="lineno" valign="top"></td></tr>
    162       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">4.  HTTP Message  . . . . . . . . . . . . . . . . . . . . . . . .  34</span></td><td> </td><td class="rblock">   <span class="insert">  6.1.  Status-Line  . . . . . . . . . . . . . . . . . . . . . . . 29</span></td><td class="lineno" valign="top"></td></tr>
    163       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">4.1.   Message Types  . . . . . . . . . . . . . . . . . . . . .  34</span></td><td> </td><td class="rblock">     <span class="insert">  6.1.1.  Status Code and Reason Phrase  . . . . . . . . . . . . 30</span></td><td class="lineno" valign="top"></td></tr>
    164       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">  4.2.   Message Headers  . . . . . . . . . . . . . . . . . . . .  34</span></td><td> </td><td class="rblock">   <span class="insert">7.  Connections  . . . . . . . . . . . . . . . . . . . . . . . . . 30</span></td><td class="lineno" valign="top"></td></tr>
    165       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">4.3.   Message Body . . . . . . . . . . . . . . . . . . . . . .  35</span></td><td> </td><td class="rblock">     <span class="insert">7.1.  Persistent Connections . . . . . . . . . . . . . . . . . . 30</span></td><td class="lineno" valign="top"></td></tr>
    166       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">4.4.   Message Length . . . . . . . . . . . . . . . . . . . . .  36</span></td><td> </td><td class="rblock">     <span class="insert">  7.1.1.  Purpose  . . . . . . . . . . . . . . . . . . . . . . . 30</span></td><td class="lineno" valign="top"></td></tr>
    167       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">4.5.   General Header Fields  . . . . . . . . . . . . . . . . .  37</span></td><td> </td><td class="rblock">     <span class="insert">  7.1.2.  Overall Operation  . . . . . . . . . . . . . . . . . . 31</span></td><td class="lineno" valign="top"></td></tr>
    168       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">5.  Request . . . . . . . . . . . . . . . . . . . . . . . . . . .  38</span></td><td> </td><td class="rblock">   <span class="insert">    7.1.3.  Proxy Servers  . . . . . . . . . . . . . . . . . . . . 33</span></td><td class="lineno" valign="top"></td></tr>
    169       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">5.1.   Request-Line . . . . . . . . . . . . . . . . . . . . . .  38</span></td><td> </td><td class="rblock">     <span class="insert">  7.1.4.  Practical Considerations . . . . . . . . . . . . . . . 33</span></td><td class="lineno" valign="top"></td></tr>
    170       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  5.1.1.   Method . . . . . . . . . . . . . . . . . . . . . . .  38</span></td><td> </td><td class="rblock">     <span class="insert">7.2.  Message Transmission Requirements  . . . . . . . . . . . . 34</span></td><td class="lineno" valign="top"></td></tr>
    171       <tr><td class="lineno" valign="top"></td><td class="lblock">       <span class="delete">5.1.2.   Request-URI  . . . . . . . . . . . . . . . . . . . .  39</span></td><td> </td><td class="rblock">       <span class="insert">7.2.1.  Persistent Connections and Flow Control  . . . . . . . 34</span></td><td class="lineno" valign="top"></td></tr>
    172       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">5.2.   The Resource Identified by a Request . . . . . . . . . .  40</span></td><td> </td><td class="rblock">     <span class="insert">  7.2.2.  Monitoring Connections for Error Status Messages . . . 34</span></td><td class="lineno" valign="top"></td></tr>
    173       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">5.3.   Request Header Fields  . . . . . . . . . . . . . . . . .  41</span></td><td> </td><td class="rblock">     <span class="insert">  7.2.3.  Use of the 100 (Continue) Status . . . . . . . . . . . 34</span></td><td class="lineno" valign="top"></td></tr>
    174       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">6.  Response  . . . . . . . . . . . . . . . . . . . . . . . . . .  42</span></td><td> </td><td class="rblock">   <span class="insert">    7.2.4.  Client Behavior if Server Prematurely Closes</span></td><td class="lineno" valign="top"></td></tr>
    175       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">6.1.   Status-Line  . . . . . . . . . . . . . . . . . . . . . .  42</span></td><td> </td><td class="rblock">     <span class="insert">          Connection . . . . . . . . . . . . . . . . . . . . . . 36</span></td><td class="lineno" valign="top"></td></tr>
    176       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">    6.1.1.   Status Code and Reason Phrase  . . . . . . . . . . .  43</span></td><td> </td><td class="rblock">   <span class="insert">8.  Header Field Definitions . . . . . . . . . . . . . . . . . . . 37</span></td><td class="lineno" valign="top"></td></tr>
    177       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">6.2.   Response Header Fields . . . . . . . . . . . . . . . . .  45</span></td><td> </td><td class="rblock">     <span class="insert">8.1.  Connection . . . . . . . . . . . . . . . . . . . . . . . . 37</span></td><td class="lineno" valign="top"></td></tr>
    178       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">7.  Entity  . . . . . . . . . . . . . . . . . . . . . . . . . . .  45</span></td><td> </td><td class="rblock">   <span class="insert">  8.2.  Content-Length . . . . . . . . . . . . . . . . . . . . . . 38</span></td><td class="lineno" valign="top"></td></tr>
    179       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">7.1.   Entity Header Fields . . . . . . . . . . . . . . . . . .  46</span></td><td> </td><td class="rblock">     <span class="insert">8.3.  Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 39</span></td><td class="lineno" valign="top"></td></tr>
    180       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">7.2.   Entity Body  . . . . . . . . . . . . . . . . . . . . . .  46</span></td><td> </td><td class="rblock">     <span class="insert">  8.3.1.  Clockless Origin Server Operation  . . . . . . . . . . 40</span></td><td class="lineno" valign="top"></td></tr>
    181       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  7.2.1.   Type . . . . . . . . . . . . . . . . . . . . . . . .  46</span></td><td> </td><td class="rblock">     <span class="insert">8.4.  Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 40</span></td><td class="lineno" valign="top"></td></tr>
    182       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  7.2.2.   Entity Length  . . . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock">     <span class="insert">8.5.  TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41</span></td><td class="lineno" valign="top"></td></tr>
    183       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">8.  Connections . . . . . . . . . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock">   <span class="insert">  8.6.  Trailer  . . . . . . . . . . . . . . . . . . . . . . . . . 42</span></td><td class="lineno" valign="top"></td></tr>
    184       <tr><td class="lineno" valign="top"></td><td class="lblock">     8.<span class="delete">1.   Persistent Connections . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock">     8.<span class="insert">7.  Transfer-Encoding  . . . . . . . . . . . . . . . . . . . . 43</span></td><td class="lineno" valign="top"></td></tr>
    185       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  8.1.1.   Purpose  . . . . . . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock">     <span class="insert">8.8.  Upgrade  . . . . . . . . . . . . . . . . . . . . . . . . . 43</span></td><td class="lineno" valign="top"></td></tr>
    186       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  8.1.2.   Overall Operation  . . . . . . . . . . . . . . . . .  48</span></td><td> </td><td class="rblock">     <span class="insert">8.9.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . . . 44</span></td><td class="lineno" valign="top"></td></tr>
    187       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">    8.1.3.   Proxy Servers  . . . . . . . . . . . . . . . . . . .  49</span></td><td> </td><td class="rblock">   <span class="insert">9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 46</span></td><td class="lineno" valign="top"></td></tr>
    188       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">    8.1.4.   Practical Considerations . . . . . . . . . . . . . .  50</span></td><td> </td><td class="rblock">   <span class="insert">10. Security Considerations  . . . . . . . . . . . . . . . . . . . 46</span></td><td class="lineno" valign="top"></td></tr>
    189       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">8.2.   Message Transmission Requirements  . . . . . . . . . . .  51</span></td><td> </td><td class="rblock">     <span class="insert">10.1. Personal Information . . . . . . . . . . . . . . . . . . . 46</span></td><td class="lineno" valign="top"></td></tr>
    190       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  8.2.1.   Persistent Connections and Flow Control  . . . . . .  51</span></td><td> </td><td class="rblock">     <span class="insert">10.2. Abuse of Server Log Information  . . . . . . . . . . . . . 46</span></td><td class="lineno" valign="top"></td></tr>
    191       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  8.2.2.   Monitoring Connections for Error Status Messages . .  51</span></td><td> </td><td class="rblock">     <span class="insert">10.3. Attacks Based On File and Path Names . . . . . . . . . . . 46</span></td><td class="lineno" valign="top"></td></tr>
    192       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  8.2.3.   Use of the 100 (Continue) Status . . . . . . . . . .  51</span></td><td> </td><td class="rblock">     <span class="insert">10.4. DNS Spoofing . . . . . . . . . . . . . . . . . . . . . . . 47</span></td><td class="lineno" valign="top"></td></tr>
    193       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">  8.2.4.   Client Behavior if Server Prematurely Closes</span></td><td> </td><td class="rblock">     <span class="insert">10.5. Proxies and Caching  . . . . . . . . . . . . . . . . . . . 47</span></td><td class="lineno" valign="top"></td></tr>
    194       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">           Connection . . . . . . . . . . . . . . . . . . . . .  53</span></td><td> </td><td class="rblock">     <span class="insert">10.6. Denial of Service Attacks on Proxies . . . . . . . . . . . 48</span></td><td class="lineno" valign="top"></td></tr>
    195       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">9.  Method Definitions  . . . . . . . . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock">   <span class="insert">11. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 48</span></td><td class="lineno" valign="top"></td></tr>
    196       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">  9.1.   Safe and Idempotent Methods  . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock">   <span class="insert">12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50</span></td><td class="lineno" valign="top"></td></tr>
    197       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">    9.1.1.   Safe Methods . . . . . . . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock">   <span class="insert">Appendix A.  Internet Media Type message/http and</span></td><td class="lineno" valign="top"></td></tr>
    198       <tr><td class="lineno" valign="top"></td><td class="lblock">       <span class="delete">9.1.2.   Idempotent Methods . . . . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock">       <span class="insert">         application/http  . . . . . . . . . . . . . . . . . . 53</span></td><td class="lineno" valign="top"></td></tr>
    199       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">  9.2.   OPTIONS  . . . . . . . . . . . . . . . . . . . . . . . .  55</span></td><td> </td><td class="rblock">   <span class="insert">Appendix B.  Tolerant Applications . . . . . . . . . . . . . . . . 54</span></td><td class="lineno" valign="top"></td></tr>
    200       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">  9.3.   GET  . . . . . . . . . . . . . . . . . . . . . . . . . .  56</span></td><td> </td><td class="rblock">   <span class="insert">Appendix C.  Conversion of Date Formats  . . . . . . . . . . . . . 55</span></td><td class="lineno" valign="top"></td></tr>
    201       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">  9.4.   HEAD . . . . . . . . . . . . . . . . . . . . . . . . . .  57</span></td><td> </td><td class="rblock">   <span class="insert">Appendix D.  Compatibility with Previous Versions  . . . . . . . . 55</span></td><td class="lineno" valign="top"></td></tr>
    202       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">9.5.   POST . . . . . . . . . . . . . . . . . . . . . . . . . .  57</span></td><td> </td><td class="rblock">     <span class="insert">D.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 56</span></td><td class="lineno" valign="top"></td></tr>
    203       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">9.6.   PUT  . . . . . . . . . . . . . . . . . . . . . . . . . .  58</span></td><td> </td><td class="rblock">     <span class="insert">  D.1.1.  Changes to Simplify Multi-homed Web Servers and</span></td><td class="lineno" valign="top"></td></tr>
    204       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">9.7.   DELETE . . . . . . . . . . . . . . . . . . . . . . . . .  59</span></td><td> </td><td class="rblock">     <span class="insert">          Conserve IP Addresses  . . . . . . . . . . . . . . . . 56</span></td><td class="lineno" valign="top"></td></tr>
    205       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">9.8.   TRACE  . . . . . . . . . . . . . . . . . . . . . . . . .  59</span></td><td> </td><td class="rblock">     <span class="insert">D.2.  Compatibility with HTTP/1.0 Persistent Connections . . . . 56</span></td><td class="lineno" valign="top"></td></tr>
    206       <tr><td class="lineno" valign="top"></td><td class="lblock">     <span class="delete">9.9.   CONNECT  . . . . . . . . . . . . . . . . . . . . . . . .  60</span></td><td> </td><td class="rblock">     <span class="insert">D.3.  Changes from RFC 2068  . . . . . . . . . . . . . . . . . . 57</span></td><td class="lineno" valign="top"></td></tr>
    207       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">10. Status Code Definitions . . . . . . . . . . . . . . . . . . .  60</span></td><td> </td><td class="rblock">   <span class="insert">Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58</span></td><td class="lineno" valign="top"></td></tr>
    208       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">  10.1.  Informational 1xx  . . . . . . . . . . . . . . . . . . .  60</span></td><td> </td><td class="rblock">   <span class="insert">Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 61</span></td><td class="lineno" valign="top"></td></tr>
    209       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">    10.1.1.  100 Continue . . . . . . . . . . . . . . . . . . . .  61</span></td><td> </td><td class="rblock">   <span class="insert">Intellectual Property and Copyright Statements . . . . . . . . . . 63</span></td><td class="lineno" valign="top"></td></tr>
     137      <tr><td class="lineno" valign="top"></td><td class="lblock">   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <span class="delete">9</span></td><td> </td><td class="rblock">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">.  5</span></td><td class="lineno" valign="top"></td></tr>
     138      <tr><td class="lineno" valign="top"></td><td class="lblock">     1.1.   Purpose  . . . . . . . . . . . . . . . . . . . . . . . .   <span class="delete">9</span></td><td> </td><td class="rblock">     1.1.  Purpose  . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">.  5</span></td><td class="lineno" valign="top"></td></tr>
     139      <tr><td class="lineno" valign="top"></td><td class="lblock">     1.2.   Requirements . . . . . . . . . . . . . . . . . . . . . .   <span class="delete">9</span></td><td> </td><td class="rblock">     1.2.  Requirements . . . . . . . . . . . . . . . . . . . . . . <span class="insert">.  6</span></td><td class="lineno" valign="top"></td></tr>
     140      <tr><td class="lineno" valign="top"></td><td class="lblock">     1.3.   Terminology  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">10</span></td><td> </td><td class="rblock">     1.3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . <span class="insert">.  6</span></td><td class="lineno" valign="top"></td></tr>
     141      <tr><td class="lineno" valign="top"></td><td class="lblock">     1.4.   Overall Operation  . . . . . . . . . . . . . . . . . . .  <span class="delete">14</span></td><td> </td><td class="rblock">     1.4.  Overall Operation  . . . . . . . . . . . . . . . . . . . <span class="insert">.  9</span></td><td class="lineno" valign="top"></td></tr>
     142      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  Notational Conventions and Generic Grammar  . . . . . . . . .  <span class="delete">16</span></td><td> </td><td class="rblock">   2.  Notational Conventions and Generic Grammar . . . . . . . . . <span class="insert">. 11</span></td><td class="lineno" valign="top"></td></tr>
     143      <tr><td class="lineno" valign="top"></td><td class="lblock">     2.1.   Augmented BNF  . . . . . . . . . . . . . . . . . . . . .  <span class="delete">16</span></td><td> </td><td class="rblock">     2.1.  Augmented BNF  . . . . . . . . . . . . . . . . . . . . . <span class="insert">. 11</span></td><td class="lineno" valign="top"></td></tr>
     144      <tr><td class="lineno" valign="top"></td><td class="lblock">     2.2.   Basic Rules  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">18</span></td><td> </td><td class="rblock">     2.2.  Basic Rules  . . . . . . . . . . . . . . . . . . . . . . <span class="insert">. 13</span></td><td class="lineno" valign="top"></td></tr>
     145      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  Protocol Parameters . . . . . . . . . . . . . . . . . . . . .  <span class="delete">20</span></td><td> </td><td class="rblock">   3.  Protocol Parameters  . . . . . . . . . . . . . . . . . . . . . <span class="insert">15</span></td><td class="lineno" valign="top"></td></tr>
     146      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.1.   HTTP Version . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">20</span></td><td> </td><td class="rblock">     3.1.  HTTP Version . . . . . . . . . . . . . . . . . . . . . . <span class="insert">. 15</span></td><td class="lineno" valign="top"></td></tr>
     147      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.2.   Uniform Resource Identifiers . . . . . . . . . . . . . .  <span class="delete">21</span></td><td> </td><td class="rblock">     3.2.  Uniform Resource Identifiers . . . . . . . . . . . . . . <span class="insert">. 16</span></td><td class="lineno" valign="top"></td></tr>
     148      <tr><td class="lineno" valign="top"></td><td class="lblock">       3.2.1.   General Syntax . . . . . . . . . . . . . . . . . . .  <span class="delete">21</span></td><td> </td><td class="rblock">       3.2.1.  General Syntax . . . . . . . . . . . . . . . . . . . <span class="insert">. 16</span></td><td class="lineno" valign="top"></td></tr>
     149      <tr><td class="lineno" valign="top"></td><td class="lblock">       3.2.2.   http URL . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">22</span></td><td> </td><td class="rblock">       3.2.2.  http URL . . . . . . . . . . . . . . . . . . . . . . <span class="insert">. 17</span></td><td class="lineno" valign="top"></td></tr>
     150      <tr><td class="lineno" valign="top"></td><td class="lblock">       3.2.3.   URI Comparison . . . . . . . . . . . . . . . . . . .  <span class="delete">22</span></td><td> </td><td class="rblock">       3.2.3.  URI Comparison . . . . . . . . . . . . . . . . . . . <span class="insert">. 17</span></td><td class="lineno" valign="top"></td></tr>
     151      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.3.   Date/Time Formats  . . . . . . . . . . . . . . . . . . .  <span class="delete">23</span></td><td> </td><td class="rblock">     3.3.  Date/Time Formats  . . . . . . . . . . . . . . . . . . . <span class="insert">. 18</span></td><td class="lineno" valign="top"></td></tr>
     152      <tr><td class="lineno" valign="top"></td><td class="lblock">       3.3.1.   Full Date  . . . . . . . . . . . . . . . . . . . . .  <span class="delete">23</span></td><td> </td><td class="rblock">       3.3.1.  Full Date  . . . . . . . . . . . . . . . . . . . . . . <span class="insert">18</span></td><td class="lineno" valign="top"></td></tr>
     153      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       3.3.2.   Delta Seconds</span>  . . . . . . . . . . . . . . . . . . .  <span class="delete">24</span></td><td> </td><td class="rblock"><span class="insert">     3.4.  Transfer Codings</span> . . . . . . . . . . . . . . . . . . . . . <span class="insert">19</span></td><td class="lineno" valign="top"></td></tr>
     154      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.4.   Character Sets</span> . . . . . . . . . . . . . . . . . . . . .  <span class="delete">24</span></td><td> </td><td class="rblock"><span class="insert">       3.4.1.  Chunked Transfer Coding</span>  . . . . . . . . . . . . . . . <span class="insert">20</span></td><td class="lineno" valign="top"></td></tr>
     155      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       3.4.1.   Missing Charset</span>  . . . . . . . . . . . . . . . . . .  <span class="delete">25</span></td><td> </td><td class="rblock"><span class="insert">   4.  HTTP Message</span> . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">22</span></td><td class="lineno" valign="top"></td></tr>
     156      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.5.   Content Codings</span>  . . . . . . . . . . . . . . . . . . . .  <span class="delete">25</span></td><td> </td><td class="rblock"><span class="insert">     4.1.  Message Types</span>  . . . . . . . . . . . . . . . . . . . . . . <span class="insert">22</span></td><td class="lineno" valign="top"></td></tr>
     157      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.6.   Transfer Codings</span> . . . . . . . . . . . . . . . . . . . .  <span class="delete">27</span></td><td> </td><td class="rblock"><span class="insert">     4.2.  Message Headers</span>  . . . . . . . . . . . . . . . . . . . . . <span class="insert">23</span></td><td class="lineno" valign="top"></td></tr>
     158      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       3.6.1.   Chunked Transfer Coding</span>  . . . . . . . . . . . . . .  <span class="delete">28</span></td><td> </td><td class="rblock"><span class="insert">     4.3.  Message Body</span> . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">24</span></td><td class="lineno" valign="top"></td></tr>
     159      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.7.   Media Types</span>  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">29</span></td><td> </td><td class="rblock"><span class="insert">     4.4.  Message Length</span> . . . . . . . . . . . . . . . . . . . . . . <span class="insert">25</span></td><td class="lineno" valign="top"></td></tr>
     160      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       3.7.1.   Canonicalization and Text Defaults</span> . . . . . . . . .  <span class="delete">30</span></td><td> </td><td class="rblock"><span class="insert">     4.5.  General Header Fields</span>  . . . . . . . . . . . . . . . . . . <span class="insert">26</span></td><td class="lineno" valign="top"></td></tr>
     161      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       3.7.2.   Multipart Types</span>  . . . . . . . . . . . . . . . . . .  <span class="delete">30</span></td><td> </td><td class="rblock"><span class="insert">   5.  Request</span>  . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">26</span></td><td class="lineno" valign="top"></td></tr>
     162      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.8.   Product Tokens</span> . . . . . . . . . . . . . . . . . . . . .  <span class="delete">31</span></td><td> </td><td class="rblock"><span class="insert">     5.1.  Request-Line</span> . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">27</span></td><td class="lineno" valign="top"></td></tr>
     163      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.9.   Quality Values</span> . . . . . . . . . . . . . . . . . . . . .  <span class="delete">32</span></td><td> </td><td class="rblock"><span class="insert">       5.1.1.  Method</span> . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">27</span></td><td class="lineno" valign="top"></td></tr>
     164      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.10.  Language Tags</span>  . . . . . . . . . . . . . . . . . . . . .  <span class="delete">32</span></td><td> </td><td class="rblock"><span class="insert">       5.1.2.  Request-URI</span>  . . . . . . . . . . . . . . . . . . . . . <span class="insert">27</span></td><td class="lineno" valign="top"></td></tr>
     165      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.11.  Entity Tags</span>  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">33</span></td><td> </td><td class="rblock"><span class="insert">     5.2.  The Resource Identified by a Request</span> . . . . . . . . . . . <span class="insert">28</span></td><td class="lineno" valign="top"></td></tr>
     166      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     3.12.  Range Units</span>  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">33</span></td><td> </td><td class="rblock"><span class="insert">   6.  Response</span> . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">29</span></td><td class="lineno" valign="top"></td></tr>
     167      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   4.  HTTP Message</span>  . . . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">34</span></td><td> </td><td class="rblock"><span class="insert">     6.1.  Status-Line</span>  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">29</span></td><td class="lineno" valign="top"></td></tr>
     168      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     4.1.   Message Types</span>  . . . . . . . . . . . . . . . . . . . . .  <span class="delete">34</span></td><td> </td><td class="rblock"><span class="insert">       6.1.1.  Status Code and Reason Phrase</span>  . . . . . . . . . . . . <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
     169      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     4.2.   Message Headers</span>  . . . . . . . . . . . . . . . . . . . .  <span class="delete">34</span></td><td> </td><td class="rblock"><span class="insert">   7.  Connections</span>  . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
     170      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     4.3.   Message Body</span> . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">35</span></td><td> </td><td class="rblock"><span class="insert">     7.1.  Persistent Connections</span> . . . . . . . . . . . . . . . . . . <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
     171      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     4.4.   Message Length</span> . . . . . . . . . . . . . . . . . . . . .  <span class="delete">36</span></td><td> </td><td class="rblock"><span class="insert">       7.1.1.  Purpose</span>  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
     172      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     4.5.   General Header Fields</span>  . . . . . . . . . . . . . . . . .  <span class="delete">37</span></td><td> </td><td class="rblock"><span class="insert">       7.1.2.  Overall Operation</span>  . . . . . . . . . . . . . . . . . . <span class="insert">31</span></td><td class="lineno" valign="top"></td></tr>
     173      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   5.  Request</span> . . . . . . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">38</span></td><td> </td><td class="rblock"><span class="insert">       7.1.3.  Proxy Servers</span>  . . . . . . . . . . . . . . . . . . . . <span class="insert">33</span></td><td class="lineno" valign="top"></td></tr>
     174      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     5.1.   Request-Line</span> . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">38</span></td><td> </td><td class="rblock"><span class="insert">       7.1.4.  Practical Considerations</span> . . . . . . . . . . . . . . . <span class="insert">33</span></td><td class="lineno" valign="top"></td></tr>
     175      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       5.1.1.   Method</span> . . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">38</span></td><td> </td><td class="rblock"><span class="insert">     7.2.  Message Transmission Requirements</span>  . . . . . . . . . . . . <span class="insert">34</span></td><td class="lineno" valign="top"></td></tr>
     176      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       5.1.2.   Request-URI</span>  . . . . . . . . . . . . . . . . . . . .  <span class="delete">39</span></td><td> </td><td class="rblock"><span class="insert">       7.2.1.  Persistent Connections and Flow Control</span>  . . . . . . . <span class="insert">34</span></td><td class="lineno" valign="top"></td></tr>
     177      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     5.2.   The Resource Identified by a Request</span> . . . . . . . . . .  <span class="delete">40</span></td><td> </td><td class="rblock"><span class="insert">       7.2.2.  Monitoring Connections for Error Status Messages</span> . . . <span class="insert">34</span></td><td class="lineno" valign="top"></td></tr>
     178      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     5.3.   Request Header Fields</span>  . . . . . . . . . . . . . . . . .  <span class="delete">41</span></td><td> </td><td class="rblock"><span class="insert">       7.2.3.  Use of the 100 (Continue) Status</span> . . . . . . . . . . . <span class="insert">34</span></td><td class="lineno" valign="top"></td></tr>
     179      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   6.  Response</span>  . . . . . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">42</span></td><td> </td><td class="rblock"><span class="insert">       7.2.4.  Client Behavior if Server Prematurely Closes</span></td><td class="lineno" valign="top"></td></tr>
     180      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     6.1.   Status-Line</span>  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">42</span></td><td> </td><td class="rblock"><span class="insert">               Connection</span> . . . . . . . . . . . . . . . . . . . . . . <span class="insert">36</span></td><td class="lineno" valign="top"></td></tr>
     181      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       6.1.1.   Status Code and Reason Phrase</span>  . . . . . . . . . . .  <span class="delete">43</span></td><td> </td><td class="rblock"><span class="insert">   8.  Header Field Definitions</span> . . . . . . . . . . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
     182      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     6.2.   Response Header Fields</span> . . . . . . . . . . . . . . . . .  <span class="delete">45</span></td><td> </td><td class="rblock"><span class="insert">     8.1.  Connection</span> . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">37</span></td><td class="lineno" valign="top"></td></tr>
     183      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   7.  Entity</span>  . . . . . . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">45</span></td><td> </td><td class="rblock"><span class="insert">     8.2.  Content-Length</span> . . . . . . . . . . . . . . . . . . . . . . <span class="insert">38</span></td><td class="lineno" valign="top"></td></tr>
     184      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     7.1.   Entity Header Fields . . . . . . . . . . . . . . . . . .  46</span></td><td> </td><td class="rblock"><span class="insert">     8.3.  Date</span> . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">39</span></td><td class="lineno" valign="top"></td></tr>
     185      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     7.2.   Entity Body  . . . . . . . . . . . . . . . . . . . . . .  46</span></td><td> </td><td class="rblock"><span class="insert">       8.3.1.  Clockless Origin Server Operation</span>  . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
     186      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       7.2.1.   Type . . . . . . . . . . . . . . . . . . . . . . . .  46</span></td><td> </td><td class="rblock"><span class="insert">     8.4.  Host</span> . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
     187      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       7.2.2.   Entity Length  . . . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock"><span class="insert">     8.5.  TE</span> . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">41</span></td><td class="lineno" valign="top"></td></tr>
     188      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   8.  Connections . . . . . . . . . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock"><span class="insert">     8.6.  Trailer</span>  . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">42</span></td><td class="lineno" valign="top"></td></tr>
     189      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     8.1.   Persistent Connections . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock"><span class="insert">     8.7.  Transfer-Encoding</span>  . . . . . . . . . . . . . . . . . . . . <span class="insert">43</span></td><td class="lineno" valign="top"></td></tr>
     190      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.1.1.   Purpose  . . . . . . . . . . . . . . . . . . . . . .  47</span></td><td> </td><td class="rblock"><span class="insert">     8.8.  Upgrade</span>  . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">43</span></td><td class="lineno" valign="top"></td></tr>
     191      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.1.2.   Overall Operation  . . . . . . . . . . . . . . . . .  48</span></td><td> </td><td class="rblock"><span class="insert">     8.9.  Via</span>  . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">44</span></td><td class="lineno" valign="top"></td></tr>
     192      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.1.3.   Proxy Servers  . . . . . . . . . . . . . . . . . . .  49</span></td><td> </td><td class="rblock"><span class="insert">   9.  IANA Considerations</span>  . . . . . . . . . . . . . . . . . . . . . <span class="insert">46</span></td><td class="lineno" valign="top"></td></tr>
     193      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.1.4.   Practical Considerations . . . . . . . . . . . . . .  50</span></td><td> </td><td class="rblock"><span class="insert">   10. Security Considerations</span>  . . . . . . . . . . . . . . . . . . . <span class="insert">46</span></td><td class="lineno" valign="top"></td></tr>
     194      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     8.2.   Message Transmission Requirements  . . . . . . . . . . .  51</span></td><td> </td><td class="rblock"><span class="insert">     10.1. Personal Information</span> . . . . . . . . . . . . . . . . . . . <span class="insert">46</span></td><td class="lineno" valign="top"></td></tr>
     195      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.2.1.   Persistent Connections and Flow Control  . . . . . .  51</span></td><td> </td><td class="rblock"><span class="insert">     10.2. Abuse of Server Log Information</span>  . . . . . . . . . . . . . <span class="insert">46</span></td><td class="lineno" valign="top"></td></tr>
     196      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.2.2.   Monitoring Connections for Error Status Messages . .  51</span></td><td> </td><td class="rblock"><span class="insert">     10.3.</span> Attacks <span class="insert">Based On File and Path Names</span> . . . . . . . . . . . <span class="insert">46</span></td><td class="lineno" valign="top"></td></tr>
     197      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.2.3.   Use of the 100 (Continue) Status . . . . . . . . . .  51</span></td><td> </td><td class="rblock"><span class="insert">     10.4. DNS Spoofing</span> . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">47</span></td><td class="lineno" valign="top"></td></tr>
     198      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       8.2.4.   Client Behavior if Server Prematurely Closes</span></td><td> </td><td class="rblock"><span class="insert">     10.5. Proxies and Caching</span>  . . . . . . . . . . . . . . . . . . . <span class="insert">47</span></td><td class="lineno" valign="top"></td></tr>
     199      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                Connection . . . . . . . . . . . . . . . . . . . . .  53</span></td><td> </td><td class="rblock"><span class="insert">     10.6. Denial of Service Attacks on Proxies</span> . . . . . . . . . . . <span class="insert">48</span></td><td class="lineno" valign="top"></td></tr>
     200      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   9.  Method Definitions  . . . . . . . . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock"><span class="insert">   11. Acknowledgments</span>  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">48</span></td><td class="lineno" valign="top"></td></tr>
     201      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.1.   Safe and Idempotent Methods  . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock"><span class="insert">   12. References</span> . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">50</span></td><td class="lineno" valign="top"></td></tr>
     202      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       9.1.1.   Safe Methods . . . . . . . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock"><span class="insert">   Appendix A.  Internet Media Type message/http and</span></td><td class="lineno" valign="top"></td></tr>
     203      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       9.1.2.   Idempotent Methods . . . . . . . . . . . . . . . . .  54</span></td><td> </td><td class="rblock"><span class="insert">                application/http</span>  . . . . . . . . . . . . . . . . . . <span class="insert">53</span></td><td class="lineno" valign="top"></td></tr>
     204      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.2.   OPTIONS  . . . . . . . . . . . . . . . . . . . . . . . .  55</span></td><td> </td><td class="rblock"><span class="insert">   Appendix B.  Tolerant Applications</span> . . . . . . . . . . . . . . . . <span class="insert">54</span></td><td class="lineno" valign="top"></td></tr>
     205      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.3.   GET  . . . . . . . . . . . . . . . . . . . . . . . . . .  56</span></td><td> </td><td class="rblock"><span class="insert">   Appendix C.</span>  Conversion of Date Formats  . . . . . . . . . . . . . <span class="insert">55</span></td><td class="lineno" valign="top"></td></tr>
     206      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.4.   HEAD . . . . . . . . . . . . . . . . . . . . . . . . . .  57</span></td><td> </td><td class="rblock"><span class="insert">   Appendix D.  Compatibility with Previous Versions</span>  . . . . . . . . <span class="insert">55</span></td><td class="lineno" valign="top"></td></tr>
     207      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.5.   POST . . . . . . . . . . . . . . . . . . . . . . . . . .  57</span></td><td> </td><td class="rblock"><span class="insert">     D.1.  Changes from HTTP/1.0</span>  . . . . . . . . . . . . . . . . . . <span class="insert">56</span></td><td class="lineno" valign="top"></td></tr>
     208      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.6.   PUT  . . . . . . . . . . . . . . . . . . . . . . . . . .  58</span></td><td> </td><td class="rblock"><span class="insert">       D.1.1.  Changes to Simplify Multi-homed Web Servers</span> and</td><td class="lineno" valign="top"></td></tr>
     209      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.7.   DELETE . . . . . . . . . . . . . . . . . . . . . . . . .  59</span></td><td> </td><td class="rblock">               <span class="insert">Conserve IP Addresses</span>  . . . . . . . . . . . . . . . . <span class="insert">56</span></td><td class="lineno" valign="top"></td></tr>
     210      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.8.   TRACE  . . . . . . . . . . . . . . . . . . . . . . . . .  59</span></td><td> </td><td class="rblock"><span class="insert">     D.2.</span>  Compatibility with HTTP/1.0 <span class="insert">Persistent Connections</span> . . . . <span class="insert">56</span></td><td class="lineno" valign="top"></td></tr>
     211      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     9.9.   CONNECT  . . . . . . . . . . . . . . . . . . . . . . . .  60</span></td><td> </td><td class="rblock"><span class="insert">     D.3.</span>  Changes from RFC 2068  . . . . . . . . . . . . . . . . . . <span class="insert">57</span></td><td class="lineno" valign="top"></td></tr>
     212      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   10. Status Code Definitions . . . . . . . . . . . . . . . . . . .  60</span></td><td> </td><td class="rblock">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">58</span></td><td class="lineno" valign="top"></td></tr>
     213      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     10.1.  Informational 1xx  . . . . . . . . . . . . . . . . . . .  60</span></td><td> </td><td class="rblock">   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">. 61</span></td><td class="lineno" valign="top"></td></tr>
     214      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       10.1.1.  100 Continue . . . . . . . . . . . . . . . . . . . .  61</span></td><td> </td><td class="rblock">   Intellectual Property and Copyright Statements . . . . . . . . . <span class="insert">. 63</span></td><td class="lineno" valign="top"></td></tr>
    210215      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       10.1.2.  101 Switching Protocols  . . . . . . . . . . . . . .  61</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    211216      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     10.2.  Successful 2xx . . . . . . . . . . . . . . . . . . . . .  61</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    347352      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.43. User-Agent . . . . . . . . . . . . . . . . . . . . . . . 148</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    348353      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.44. Vary . . . . . . . . . . . . . . . . . . . . . . . . . . 148</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    349       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.45. Via  . . . . . . . . . . . . . . . . . . . . . . . . . . 149</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    350       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.46. Warning  . . . . . . . . . . . . . . . . . . . . . . . . 150</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    351       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.47. WWW-Authenticate . . . . . . . . . . . . . . . . . . . . 153</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    352       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   15. Security Considerations . . . . . . . . . . . . . . . . . . . 153</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    353       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.1.  Personal Information . . . . . . . . . . . . . . . . . . 153</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    354       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.1.  Abuse of Server Log Information  . . . . . . . . . . 154</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    355       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.2.  Transfer of Sensitive Information  . . . . . . . . . 154</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    356       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.3.  Encoding Sensitive Information in URI's  . . . . . . 155</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    357       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.4.  Privacy Issues Connected to Accept Headers . . . . . 155</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    358       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.2.  Attacks Based On File and Path Names . . . . . . . . . . 156</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    359       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.3.  DNS Spoofing . . . . . . . . . . . . . . . . . . . . . . 156</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    360       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.4.  Location Headers and Spoofing  . . . . . . . . . . . . . 157</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    361       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.5.  Content-Disposition Issues . . . . . . . . . . . . . . . 157</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    362       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.6.  Authentication Credentials and Idle Clients  . . . . . . 157</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    363       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.7.  Proxies and Caching  . . . . . . . . . . . . . . . . . . 158</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    364       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.7.1.  Denial of Service Attacks on Proxies . . . . . . . . 159</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    365       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 159</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    366       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   17. References  . . . . . . . . . . . . . . . . . . . . . . . . . 161</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    367       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Appendix A.  Appendices . . . . . . . . . . . . . . . . . . . . . 165</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    368       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.1.   Internet Media Type message/http and application/http  . 165</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    369       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.2.   Internet Media Type multipart/byteranges . . . . . . . . 166</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    370       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.3.   Tolerant Applications  . . . . . . . . . . . . . . . . . 167</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     354      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.45. Via</span>  . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">149</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     355      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.46. Warning</span>  . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">150</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     356      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     14.47. WWW-Authenticate</span> . . . . . . . . . . . . . . . . . . . . <span class="delete">153</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     357      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   15. Security Considerations</span> . . . . . . . . . . . . . . . . . . . <span class="delete">153</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     358      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.1.  Personal Information</span> . . . . . . . . . . . . . . . . . . <span class="delete">153</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     359      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.1.  Abuse of Server Log Information</span>  . . . . . . . . . . <span class="delete">154</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     360      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.2.  Transfer of Sensitive Information</span>  . . . . . . . . . <span class="delete">154</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     361      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.3.  Encoding Sensitive Information in URI's</span>  . . . . . . <span class="delete">155</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     362      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.1.4.  Privacy Issues Connected to Accept Headers</span> . . . . . <span class="delete">155</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     363      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.2.  Attacks Based On File and Path Names</span> . . . . . . . . . . <span class="delete">156</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     364      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.3.  DNS Spoofing</span> . . . . . . . . . . . . . . . . . . . . . . <span class="delete">156</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     365      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.4.  Location Headers and Spoofing</span>  . . . . . . . . . . . . . <span class="delete">157</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     366      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.5.  Content-Disposition Issues</span> . . . . . . . . . . . . . . . <span class="delete">157</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     367      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.6.  Authentication Credentials and Idle Clients</span>  . . . . . . <span class="delete">157</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     368      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     15.7.  Proxies and Caching</span>  . . . . . . . . . . . . . . . . . . <span class="delete">158</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     369      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       15.7.1.  Denial of Service</span> Attacks <span class="delete">on Proxies . . . . . . . . 159</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     370      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   16. Acknowledgments . . . .</span> . . . . . . . . . . . . . . . . . . . <span class="delete">159</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     371      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   17. References</span>  . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">161</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     372      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Appendix A.  Appendices</span> . . . . . . . . . . . . . . . . . . . . . <span class="delete">165</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     373      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.1.   Internet Media Type message/http and application/http</span>  . <span class="delete">165</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     374      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.2.   Internet Media Type multipart/byteranges</span> . . . . . . . . <span class="delete">166</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     375      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.3.   Tolerant Applications</span>  . . . . . . . . . . . . . . . . . <span class="delete">167</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    371376      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.4.   Differences Between HTTP Entities and RFC 2045</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    372       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">            Entities . . . . . . . . . . . . . . . . . . . . . . . . 168</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    373       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.1.   MIME-Version . . . . . . . . . . . . . . . . . . . . 169</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    374       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.2.   Conversion to Canonical Form . . . . . . . . . . . . 169</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    375       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.3.   Conversion of Date Formats . . . . . . . . . . . . . 169</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    376       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.4.   Introduction of Content-Encoding . . . . . . . . . . 170</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    377       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.5.   No Content-Transfer-Encoding . . . . . . . . . . . . 170</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    378       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.6.   Introduction of Transfer-Encoding  . . . . . . . . . 170</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    379       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.7.   MHTML and Line Length Limitations  . . . . . . . . . 171</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     377      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">            Entities</span> . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">168</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     378      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.1.   MIME-Version</span> . . . . . . . . . . . . . . . . . . . . <span class="delete">169</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     379      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.2.   Conversion to Canonical Form</span> . . . . . . . . . . . . <span class="delete">169</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     380      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.3.</span>   Conversion of Date Formats . . . . . . . . . . . . . <span class="delete">169</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     381      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.4.   Introduction of Content-Encoding . . . . .</span> . . . . . <span class="delete">170</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     382      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.5.   No Content-Transfer-Encoding</span> . . . . . . . . . . . . <span class="delete">170</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     383      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.6.   Introduction of Transfer-Encoding</span>  . . . . . . . . . <span class="delete">170</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     384      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.4.7.   MHTML</span> and <span class="delete">Line Length Limitations  . . . . . . . . . 171</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    380385      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.5.   Additional Features  . . . . . . . . . . . . . . . . . . 171</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    381       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.5.1.   Content-Disposition  . . . . . . . . . . . . . . . . 171</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    382       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.6.   Compatibility with Previous Versions . . . . . . . . . . 172</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    383       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.6.1.   Changes from HTTP/1.0  . . . . . . . . . . . . . . . 173</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     386      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.5.1.   Content-Disposition</span>  . . . . . . . . . . . . . . . . <span class="delete">171</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     387      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">     A.6.</span>   Compatibility with <span class="delete">Previous Versions . . . . . . . . . . 172</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     388      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.6.1.   Changes from</span> HTTP/1.0  . . . . <span class="delete">. . . . . . . . . . . 173</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    384389      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.6.2.   Compatibility with HTTP/1.0 Persistent Connections . 174</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    385       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.6.3.   Changes from RFC 2068  . . . . . . . . . . . . . . . 174</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    386       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Appendix B.  Index  . . . . . . . . . . . . . . . . . . . . . . . 177</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    387       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    388       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . 188</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    389       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Intellectual Property and Copyright Statements  . . . . . . . . . 190</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     390      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       A.6.3.</span>   Changes from RFC 2068  . . . . . . . . . . . . . . . <span class="delete">174</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     391      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Appendix B.  Index  . . . . . . . . . . . . . . . . . .</span> . . . <span class="delete">. . 177</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     392      <tr><td class="lineno" valign="top"></td><td class="lblock">   Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">177</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     393      <tr><td class="lineno" valign="top"></td><td class="lblock">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">188</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     394      <tr><td class="lineno" valign="top"></td><td class="lblock">   Intellectual Property and Copyright Statements  . . . . . . . . . <span class="delete">190</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    390395      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    391396      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
    392397      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    393398      <tr><td><a name="diff0010" /></td></tr>
    394       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   This document will define aspects of HTTP related to overall network</span></td><td class="lineno" valign="top"></td></tr>
     399      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">This document will define aspects of HTTP related to overall network</span></td><td class="lineno" valign="top"></td></tr>
    395400      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   operation, message framing, interaction with transport protocols, and</span></td><td class="lineno" valign="top"></td></tr>
    396401      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   URI schemes.  Right now it only includes the extracted relevant</span></td><td class="lineno" valign="top"></td></tr>
    397402      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   sections of [RFC2616].</span></td><td class="lineno" valign="top"></td></tr>
    398       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                                                                         </span></td><td class="lineno" valign="top"></td></tr>
     403      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
    399404      <tr><td class="lineno" valign="top"></td><td class="left">1.1.  Purpose</td><td> </td><td class="right">1.1.  Purpose</td><td class="lineno" valign="top"></td></tr>
    400405      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    432437      <tr><td class="lineno" valign="top"></td><td class="left">      An entity included with a response that is subject to content</td><td> </td><td class="right">      An entity included with a response that is subject to content</td><td class="lineno" valign="top"></td></tr>
    433438      <tr><td><a name="diff0014" /></td></tr>
    434       <tr><td class="lineno" valign="top"></td><td class="lblock">      negotiation, as described in Section <span class="delete">12.  There may exist multiple</span></td><td> </td><td class="rblock">      negotiation, as described in Section <span class="insert">4 of [Part3].  There may</span></td><td class="lineno" valign="top"></td></tr>
    435       <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">representations associated with a particular response status.</span></td><td> </td><td class="rblock">      <span class="insert">exist multiple representations associated with a particular</span></td><td class="lineno" valign="top"></td></tr>
    436       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">      response status.</span></td><td class="lineno" valign="top"></td></tr>
     439      <tr><td class="lineno" valign="top"></td><td class="lblock">      negotiation, as described in Section <span class="delete">12.</span>  There may exist multiple</td><td> </td><td class="rblock">      negotiation, as described in Section <span class="insert">4 of [Part3].</span>  There may</td><td class="lineno" valign="top"></td></tr>
     440      <tr><td class="lineno" valign="top"></td><td class="lblock">      representations associated with a particular response status.</td><td> </td><td class="rblock">      exist multiple representations associated with a particular</td><td class="lineno" valign="top"></td></tr>
     441      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">      response status.</td><td class="lineno" valign="top"></td></tr>
    437442      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    438443      <tr><td class="lineno" valign="top"></td><td class="left">   content negotiation</td><td> </td><td class="right">   content negotiation</td><td class="lineno" valign="top"></td></tr>
     
    469474      <tr><td class="lineno" valign="top"></td><td class="left">      The rules for determining the cacheability of HTTP responses are</td><td> </td><td class="right">      The rules for determining the cacheability of HTTP responses are</td><td class="lineno" valign="top"></td></tr>
    470475      <tr><td><a name="diff0017" /></td></tr>
    471       <tr><td class="lineno" valign="top"></td><td class="lblock">      defined in Section <span class="delete">13.  Even if a resource is cacheable, there may</span></td><td> </td><td class="rblock">      defined in Section <span class="insert">2 of [Part6].  Even if a resource is cacheable,</span></td><td class="lineno" valign="top"></td></tr>
    472       <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">be additional constraints on whether a cache can use the cached</span></td><td> </td><td class="rblock">      <span class="insert">there may be additional constraints on whether a cache can use the</span></td><td class="lineno" valign="top"></td></tr>
    473       <tr><td class="lineno" valign="top"></td><td class="lblock">      copy for a particular request.</td><td> </td><td class="rblock">      c<span class="insert">ached c</span>opy for a particular request.</td><td class="lineno" valign="top"></td></tr>
    474       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    475       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   first-hand</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     476      <tr><td class="lineno" valign="top"></td><td class="lblock">      defined in Section <span class="delete">13.</span>  Even if a resource is cacheable, there may</td><td> </td><td class="rblock">      defined in Section <span class="insert">2 of [Part6].</span>  Even if a resource is cacheable,</td><td class="lineno" valign="top"></td></tr>
     477      <tr><td class="lineno" valign="top"></td><td class="lblock">      be additional constraints on whether a cache can use the cached</td><td> </td><td class="rblock">      there may be additional constraints on whether a cache can use the</td><td class="lineno" valign="top"></td></tr>
     478      <tr><td class="lineno" valign="top"></td><td class="lblock">      copy for a particular request.</td><td> </td><td class="rblock">      cached copy for a particular request.</td><td class="lineno" valign="top"></td></tr>
     479      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     480      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">first-hand</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    476481      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      A response is first-hand if it comes directly and without</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    477482      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      unnecessary delay from the origin server, perhaps via one or more</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    478483      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      proxies.  A response is also first-hand if its validity has just</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    479484      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      been checked directly with the origin server.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    480       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     485      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    481486      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   explicit expiration time</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    482       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     487      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    483488      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      The time at which the origin server intends that an entity should</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    484489      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      no longer be returned by a cache without further validation.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    485       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     490      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    486491      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   heuristic expiration time</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    487       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     492      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    488493      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      An expiration time assigned by a cache when no explicit expiration</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    489494      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      time is available.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    490       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     495      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    491496      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   age</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    492       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     497      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    493498      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      The age of a response is the time since it was sent by, or</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    494499      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      successfully validated with, the origin server.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    495       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     500      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    496501      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   freshness lifetime</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    497       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     502      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    498503      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      The length of time between the generation of a response and its</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    499504      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      expiration time.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    500       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     505      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    501506      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   fresh</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    502       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     507      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    503508      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      A response is fresh if its age has not yet exceeded its freshness</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    504509      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      lifetime.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    505       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     510      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    506511      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   stale</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    507       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     512      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    508513      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      A response is stale if its age has passed its freshness lifetime.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    509       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     514      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    510515      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   semantically transparent</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    511       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     516      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    512517      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      A cache behaves in a "semantically transparent" manner, with</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    513518      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      respect to a particular response, when its use affects neither the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    517522      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      that it would have received had its request been handled directly</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    518523      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      by the origin server.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    519       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     524      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    520525      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   validator</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    521       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     526      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    522527      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      A protocol element (e.g., an entity tag or a Last-Modified time)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    523528      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      that is used to find out whether a cache entry is an equivalent</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    618623      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all</td><td> </td><td class="right">   HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all</td><td class="lineno" valign="top"></td></tr>
    619624      <tr><td><a name="diff0021" /></td></tr>
    620       <tr><td class="lineno" valign="top"></td><td class="lblock">   protocol elements except the entity-body (see Appendix <span class="delete">A.3 for</span></td><td> </td><td class="rblock">   protocol elements except the entity-body (see Appendix <span class="insert">B for tolerant</span></td><td class="lineno" valign="top"></td></tr>
    621       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">tolerant applications).  The end-of-line marker within an entity-body</span></td><td> </td><td class="rblock">   <span class="insert">applications).  The end-of-line marker within an entity-body is</span></td><td class="lineno" valign="top"></td></tr>
    622       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">is defined by its associated media type, as described in Section 3.7</span>.</td><td> </td><td class="rblock">   <span class="insert">defined by its associated media type, as described in [Part3]</span>.</td><td class="lineno" valign="top"></td></tr>
     625      <tr><td class="lineno" valign="top"></td><td class="lblock">   protocol elements except the entity-body (see Appendix <span class="delete">A.3</span> for</td><td> </td><td class="rblock">   protocol elements except the entity-body (see Appendix <span class="insert">B</span> for tolerant</td><td class="lineno" valign="top"></td></tr>
     626      <tr><td class="lineno" valign="top"></td><td class="lblock">   tolerant applications).  The end-of-line marker within an entity-body</td><td> </td><td class="rblock">   applications).  The end-of-line marker within an entity-body is</td><td class="lineno" valign="top"></td></tr>
     627      <tr><td class="lineno" valign="top"></td><td class="lblock">   is defined by its associated media type, as described in <span class="delete">Section 3.7.</span></td><td> </td><td class="rblock">   defined by its associated media type, as described in <span class="insert">[Part3].</span></td><td class="lineno" valign="top"></td></tr>
    623628      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    624629      <tr><td class="lineno" valign="top"></td><td class="left">       CRLF           = CR LF</td><td> </td><td class="right">       CRLF           = CR LF</td><td class="lineno" valign="top"></td></tr>
     
    720725      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    721726      <tr><td><a name="diff0026" /></td></tr>
    722       <tr><td class="lineno" valign="top"></td><td class="lblock">3.<span class="delete">3.2.  Delta Second</span>s</td><td> </td><td class="rblock">3.<span class="insert">4.  Transfer Coding</span>s</td><td class="lineno" valign="top"></td></tr>
    723       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     727      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.3.2.  Delta Seconds</span></td><td> </td><td class="rblock">3.4.  Transfer Codings</td><td class="lineno" valign="top"></td></tr>
     728      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    724729      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Some HTTP header fields allow a time value to be specified as an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    725730      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   integer number of seconds, represented in decimal, after the time</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    726731      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   that the message was received.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    727       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     732      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    728733      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       delta-seconds  = 1*DIGIT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    729       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    730       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.4.  Character Sets</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    731       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     734      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     735      <tr><td class="lineno" valign="top"></td><td class="lblock">3.4.  <span class="delete">Character Sets</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     736      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    732737      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP uses the same definition of the term "character set" as that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    733738      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   described for MIME:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    734       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     739      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    735740      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The term "character set" is used in this document to refer to a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    736741      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   method used with one or more tables to convert a sequence of octets</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    746751      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to characters.  In particular, use of external profiling information</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    747752      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to determine the exact mapping is not permitted.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    748       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     753      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    749754      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: This use of the term "character set" is more commonly</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    750755      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      referred to as a "character encoding."  However, since HTTP and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    751756      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      MIME share the same registry, it is important that the terminology</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    752757      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      also be shared.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    753       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     758      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    754759      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP character sets are identified by case-insensitive tokens.  The</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    755760      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   complete set of tokens is defined by the IANA Character Set registry</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    756761      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   [RFC1700].</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    757       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     762      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    758763      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       charset = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    759       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     764      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    760765      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Although HTTP allows an arbitrary token to be used as a charset</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    761766      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   value, any token that has a predefined value within the IANA</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    763768      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   defined by that registry.  Applications SHOULD limit their use of</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    764769      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   character sets to those defined by the IANA registry.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    765       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     770      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    766771      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Implementors should be aware of IETF character set requirements</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    767772      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   [RFC2279] [RFC2277].</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    768       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     773      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    769774      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.4.1.  Missing Charset</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    770       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     775      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    771776      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Some HTTP/1.0 software has interpreted a Content-Type header without</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    772777      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   charset parameter incorrectly to mean "recipient should guess."</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    774779      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   parameter even when the charset is ISO-8859-1 and SHOULD do so when</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    775780      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   it is known that it will not confuse the recipient.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    776       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     781      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    777782      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Unfortunately, some older HTTP/1.0 clients did not deal properly with</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    778783      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   an explicit charset parameter.  HTTP/1.1 recipients MUST respect the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    782787      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   recipient's preference, when initially displaying a document.  See</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    783788      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Section 3.7.1.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    784       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     789      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    785790      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.5.  Content Codings</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    786       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     791      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    787792      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Content coding values indicate an encoding transformation that has</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    788793      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   been or can be applied to an entity.  Content codings are primarily</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    791796      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   and without loss of information.  Frequently, the entity is stored in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    792797      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   coded form, transmitted directly, and only decoded by the recipient.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    793       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     798      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    794799      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       content-coding   = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    795       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     800      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    796801      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   All content-coding values are case-insensitive.  HTTP/1.1 uses</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    797802      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   content-coding values in the Accept-Encoding (Section 14.3) and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    800805      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   indicates what decoding mechanism will be required to remove the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    801806      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   encoding.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    802       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     807      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    803808      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The Internet Assigned Numbers Authority (IANA) acts as a registry for</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    804809      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   content-coding value tokens.  Initially, the registry contains the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    805810      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   following tokens:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    806       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     811      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    807812      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   gzip</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    808       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     813      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    809814      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      An encoding format produced by the file compression program "gzip"</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    810815      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      (GNU zip) as described in RFC 1952 [RFC1952].  This format is a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    811816      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Lempel-Ziv coding (LZ77) with a 32 bit CRC.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    812       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     817      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    813818      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   compress</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    814       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     819      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    815820      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      The encoding format produced by the common UNIX file compression</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    816821      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      program "compress".  This format is an adaptive Lempel-Ziv-Welch</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    817822      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      coding (LZW).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    818       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     823      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    819824      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Use of program names for the identification of encoding formats is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    820825      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      not desirable and is discouraged for future encodings.  Their use</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    823828      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      applications SHOULD consider "x-gzip" and "x-compress" to be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    824829      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      equivalent to "gzip" and "compress" respectively.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    825       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     830      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    826831      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   deflate</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    827       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     832      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    828833      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      The "zlib" format defined in RFC 1950 [RFC1950] in combination</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    829834      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      with the "deflate" compression mechanism described in RFC 1951</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    830835      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      [RFC1951].</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    831       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     836      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    832837      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   identity</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    833       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     838      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    834839      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      The default (identity) encoding; the use of no transformation</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    835840      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      whatsoever.  This content-coding is used only in the Accept-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    836841      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Encoding header, and SHOULD NOT be used in the Content-Encoding</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    837842      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      header.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    838       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     843      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    839844      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   New content-coding value tokens SHOULD be registered; to allow</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    840845      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   interoperability between clients and servers, specifications of the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    842847      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   publicly available and adequate for independent implementation, and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    843848      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   conform to the purpose of content coding defined in this section.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    844       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    845       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.6.  Transfer Codings</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     849      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     850      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.6.</span>  Transfer Codings</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    846851      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    847852      <tr><td class="lineno" valign="top"></td><td class="left">   Transfer-coding values are used to indicate an encoding</td><td> </td><td class="right">   Transfer-coding values are used to indicate an encoding</td><td class="lineno" valign="top"></td></tr>
     
    862867      <tr><td class="lineno" valign="top"></td><td class="left">   All transfer-coding values are case-insensitive.  HTTP/1.1 uses</td><td> </td><td class="right">   All transfer-coding values are case-insensitive.  HTTP/1.1 uses</td><td class="lineno" valign="top"></td></tr>
    863868      <tr><td><a name="diff0027" /></td></tr>
    864       <tr><td class="lineno" valign="top"></td><td class="lblock">   transfer-coding values in the TE header field (Section <span class="delete">14.39</span>) and in</td><td> </td><td class="rblock">   transfer-coding values in the TE header field (Section <span class="insert">8.5</span>) and in</td><td class="lineno" valign="top"></td></tr>
    865       <tr><td class="lineno" valign="top"></td><td class="lblock">   the Transfer-Encoding header field (Section <span class="delete">14.41</span>).</td><td> </td><td class="rblock">   the Transfer-Encoding header field (Section <span class="insert">8.7</span>).</td><td class="lineno" valign="top"></td></tr>
     869      <tr><td class="lineno" valign="top"></td><td class="lblock">   transfer-coding values in the TE header field (Section <span class="delete">14.39)</span> and in</td><td> </td><td class="rblock">   transfer-coding values in the TE header field (Section <span class="insert">8.5)</span> and in</td><td class="lineno" valign="top"></td></tr>
     870      <tr><td class="lineno" valign="top"></td><td class="lblock">   the Transfer-Encoding header field (Section <span class="delete">14.41).</span></td><td> </td><td class="rblock">   the Transfer-Encoding header field (Section <span class="insert">8.7).</span></td><td class="lineno" valign="top"></td></tr>
    866871      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    867872      <tr><td class="lineno" valign="top"></td><td class="left">   Whenever a transfer-coding is applied to a message-body, the set of</td><td> </td><td class="right">   Whenever a transfer-coding is applied to a message-body, the set of</td><td class="lineno" valign="top"></td></tr>
     
    879884      <tr><td class="lineno" valign="top"></td><td class="left">   protocol.  In HTTP, the only unsafe characteristic of message-bodies</td><td> </td><td class="right">   protocol.  In HTTP, the only unsafe characteristic of message-bodies</td><td class="lineno" valign="top"></td></tr>
    880885      <tr><td><a name="diff0028" /></td></tr>
    881       <tr><td class="lineno" valign="top"></td><td class="lblock">   is the difficulty in determining the exact body length</td><td> </td><td class="rblock">   is the difficulty in determining the exact body length<span class="insert"> (Section 4.4),</span></td><td class="lineno" valign="top"></td></tr>
    882       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">(Section 7.2.2), or the desire to encrypt data over a shared</span></td><td> </td><td class="rblock">   <span class="insert">or the desire to encrypt data over a shared transport.</span></td><td class="lineno" valign="top"></td></tr>
    883       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   transport.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     886      <tr><td class="lineno" valign="top"></td><td class="lblock">   is the difficulty in determining the exact body length</td><td> </td><td class="rblock">   is the difficulty in determining the exact body length (Section <span class="insert">4.4),</span></td><td class="lineno" valign="top"></td></tr>
     887      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">7.2.2),</span> or the desire to encrypt data over a shared</td><td> </td><td class="rblock">   or the desire to encrypt data over a shared transport.</td><td class="lineno" valign="top"></td></tr>
     888      <tr><td class="lineno" valign="top"></td><td class="lblock">   transport.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    884889      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    885890      <tr><td class="lineno" valign="top"></td><td class="left">   The Internet Assigned Numbers Authority (IANA) acts as a registry for</td><td> </td><td class="right">   The Internet Assigned Numbers Authority (IANA) acts as a registry for</td><td class="lineno" valign="top"></td></tr>
    886891      <tr><td class="lineno" valign="top"></td><td class="left">   transfer-coding value tokens.  Initially, the registry contains the</td><td> </td><td class="right">   transfer-coding value tokens.  Initially, the registry contains the</td><td class="lineno" valign="top"></td></tr>
    887892      <tr><td><a name="diff0029" /></td></tr>
    888       <tr><td class="lineno" valign="top"></td><td class="lblock">   following tokens: "chunked" (Section 3.<span class="delete">6</span>.1), "identity" (section</td><td> </td><td class="rblock">   following tokens: "chunked" (Section 3.<span class="insert">4</span>.1), "identity" (section</td><td class="lineno" valign="top"></td></tr>
    889       <tr><td class="lineno" valign="top"></td><td class="lblock">   3.6.2), "gzip" (<span class="delete">Section 3.5), "compress" (Section 3.5</span>), and "deflate"</td><td> </td><td class="rblock">   3.6.2), "gzip" (<span class="insert">[Part3]), "compress" ([Part3]</span>), and "deflate"</td><td class="lineno" valign="top"></td></tr>
    890       <tr><td class="lineno" valign="top"></td><td class="lblock">   (<span class="delete">Section 3.5</span>).</td><td> </td><td class="rblock">   (<span class="insert">[Part3]</span>).</td><td class="lineno" valign="top"></td></tr>
     893      <tr><td class="lineno" valign="top"></td><td class="lblock">   following tokens: "chunked" (Section <span class="delete">3.6.1),</span> "identity" (section</td><td> </td><td class="rblock">   following tokens: "chunked" (Section <span class="insert">3.4.1),</span> "identity" (section</td><td class="lineno" valign="top"></td></tr>
     894      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.6.2), "gzip" <span class="delete">(Section 3.5),</span> "compress" <span class="delete">(Section 3.5),</span> and "deflate"</td><td> </td><td class="rblock">   3.6.2), "gzip" <span class="insert">([Part3]),</span> "compress" <span class="insert">([Part3]),</span> and "deflate"</td><td class="lineno" valign="top"></td></tr>
     895      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">(Section 3.5).</span></td><td> </td><td class="rblock">   <span class="insert">([Part3]).</span></td><td class="lineno" valign="top"></td></tr>
    891896      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    892897      <tr><td class="lineno" valign="top"></td><td class="left">   New transfer-coding value tokens SHOULD be registered in the same way</td><td> </td><td class="right">   New transfer-coding value tokens SHOULD be registered in the same way</td><td class="lineno" valign="top"></td></tr>
     
    933938      <tr><td class="lineno" valign="top"></td><td class="left">       is acceptable in the transfer-coding of the response, as</td><td> </td><td class="right">       is acceptable in the transfer-coding of the response, as</td><td class="lineno" valign="top"></td></tr>
    934939      <tr><td><a name="diff0033" /></td></tr>
    935       <tr><td class="lineno" valign="top"></td><td class="lblock">       described in Section <span class="delete">14.39</span>; or,</td><td> </td><td class="rblock">       described in Section <span class="insert">8.5</span>; or,</td><td class="lineno" valign="top"></td></tr>
    936       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                                                                         </span></td><td class="lineno" valign="top"></td></tr>
     940      <tr><td class="lineno" valign="top"></td><td class="lblock">       described in Section <span class="delete">14.39;</span> or,</td><td> </td><td class="rblock">       described in Section <span class="insert">8.5;</span> or,</td><td class="lineno" valign="top"></td></tr>
     941      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
    937942      <tr><td class="lineno" valign="top"></td><td class="left">   2.  the server is the origin server for the response, the trailer</td><td> </td><td class="right">   2.  the server is the origin server for the response, the trailer</td><td class="lineno" valign="top"></td></tr>
    938943      <tr><td class="lineno" valign="top"></td><td class="left">       fields consist entirely of optional metadata, and the recipient</td><td> </td><td class="right">       fields consist entirely of optional metadata, and the recipient</td><td class="lineno" valign="top"></td></tr>
     
    950955      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    951956      <tr><td><a name="diff0034" /></td></tr>
    952       <tr><td class="lineno" valign="top"></td><td class="lblock">   A<span class="delete">n example process for decoding a Chunked-Body is presented in</span></td><td> </td><td class="rblock">   A<span class="insert"> process for decoding the "chunked" transfer-coding can be</span></td><td class="lineno" valign="top"></td></tr>
    953       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Appendix A.4.6.</span></td><td> </td><td class="rblock">   <span class="insert">represented in pseudo-code as:</span></td><td class="lineno" valign="top"></td></tr>
    954       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                                                                         </span></td><td class="lineno" valign="top"></td></tr>
     957      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">An example</span> process for decoding <span class="delete">a Chunked-Body is presented</span> in</td><td> </td><td class="rblock">   <span class="insert">A</span> process for decoding <span class="insert">the "chunked" transfer-coding can be</span></td><td class="lineno" valign="top"></td></tr>
     958      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Appendix A.4.6.</span></td><td> </td><td class="rblock"><span class="insert">   represented</span> in <span class="insert">pseudo-code as:</span></td><td class="lineno" valign="top"></td></tr>
     959      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
    955960      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       length := 0</span></td><td class="lineno" valign="top"></td></tr>
    956961      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       read chunk-size, chunk-extension (if any) and CRLF</span></td><td class="lineno" valign="top"></td></tr>
     
    975980      <tr><td><a name="diff0035" /></td></tr>
    976981      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.7.  Media Types</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    977       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     982      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    978983      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP uses Internet Media Types [RFC1590] in the Content-Type</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    979984      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   (Section 14.17) and Accept (Section 14.1) header fields in order to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    980985      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   provide open and extensible data typing and type negotiation.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    981       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     986      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    982987      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       media-type     = type "/" subtype *( ";" parameter )</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    983988      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       type           = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    984989      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       subtype        = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    985       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     990      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    986991      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Parameters MAY follow the type/subtype in the form of attribute/value</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    987992      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   pairs (as defined in Section 3.6).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    988       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     993      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    989994      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The type, subtype, and parameter attribute names are case-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    990995      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   insensitive.  Parameter values might or might not be case-sensitive,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    994999      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   might be significant to the processing of a media-type, depending on</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    9951000      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   its definition within the media type registry.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    996       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1001      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    9971002      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Note that some older HTTP applications do not recognize media type</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    9981003      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   parameters.  When sending data to older HTTP applications,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    9991004      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   implementations SHOULD only use media type parameters when they are</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10001005      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   required by that type/subtype definition.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1001       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1006      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10021007      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Media-type values are registered with the Internet Assigned Number</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10031008      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Authority (IANA [RFC1700]).  The media type registration process is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10041009      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   outlined in RFC 1590 [RFC1590].  Use of non-registered media types is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10051010      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   discouraged.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1006       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1011      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10071012      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.7.1.  Canonicalization and Text Defaults</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1008       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1013      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10091014      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Internet media types are registered with a canonical form.  An</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10101015      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity-body transferred via HTTP messages MUST be represented in the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10111016      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   appropriate canonical form prior to its transmission except for</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10121017      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   "text" types, as defined in the next paragraph.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1013       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1018      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10141019      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   When in canonical form, media subtypes of the "text" type use CRLF as</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10151020      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the text line break.  HTTP relaxes this requirement and allows the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10261031      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   or LF MUST NOT be substituted for CRLF within any of the HTTP control</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10271032      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   structures (such as header fields and multipart boundaries).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1028       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1033      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10291034      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If an entity-body is encoded with a content-coding, the underlying</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10301035      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   data MUST be in a form defined above prior to being encoded.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1031       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1036      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10321037      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The "charset" parameter is used with some media types to define the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10331038      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   character set (Section 3.4) of the data.  When no explicit charset</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10371042      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   its subsets MUST be labeled with an appropriate charset value.  See</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10381043      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Section 3.4.1 for compatibility problems.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1039       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1044      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10401045      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.7.2.  Multipart Types</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1041       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1046      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10421047      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   MIME provides for a number of "multipart" types -- encapsulations of</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10431048      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   one or more entities within a single message-body.  All multipart</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10521057      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   message-body, wherein the "end" of the message-body is indicated by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10531058      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the ending multipart boundary.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1054       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1059      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10551060      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   In general, HTTP treats a multipart message-body no differently than</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10561061      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   any other media type: strictly as payload.  The one exception is the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10631068      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   body do not have any significance to HTTP beyond that defined by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10641069      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   their MIME semantics.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1065       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1070      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10661071      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   In general, an HTTP user agent SHOULD follow the same or similar</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10671072      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   behavior as a MIME user agent would upon receipt of a multipart type.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10681073      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If an application receives an unrecognized multipart subtype, the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10691074      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   application MUST treat it as being equivalent to "multipart/mixed".</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1070       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1075      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10711076      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: The "multipart/form-data" type has been specifically defined</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10721077      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      for carrying form data suitable for processing via the POST</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10731078      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      request method, as described in RFC 1867 [RFC1867].</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1074       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1079      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10751080      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.8.  Product Tokens</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1076       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1081      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10771082      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Product tokens are used to allow communicating applications to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10781083      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   identify themselves by software name and version.  Most fields using</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10811086      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   convention, the products are listed in order of their significance</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10821087      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   for identifying the application.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1083       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1088      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10841089      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       product         = token ["/" product-version]</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10851090      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       product-version = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1086       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1091      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10871092      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Examples:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1088       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1093      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10891094      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       User-Agent: CERN-LineMode/2.15 libwww/2.17b3</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10901095      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       Server: Apache/0.8.4</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1091       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1096      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10921097      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Product tokens SHOULD be short and to the point.  They MUST NOT be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10931098      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   used for advertising or other non-essential information.  Although</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    10961101      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   versions of the same product SHOULD only differ in the product-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10971102      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   version portion of the product value).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1098       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1103      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    10991104      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.9.  Quality Values</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1100       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1105      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11011106      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP content negotiation (Section 12) uses short "floating point"</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11021107      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   numbers to indicate the relative importance ("weight") of various</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    11081113      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   decimal point.  User configuration of these values SHOULD also be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11091114      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   limited in this fashion.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1110       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1115      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11111116      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       qvalue         = ( "0" [ "." 0*3DIGIT ] )</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11121117      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | ( "1" [ "." 0*3("0") ] )</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1113       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1118      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11141119      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   "Quality values" is a misnomer, since these values merely represent</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11151120      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   relative degradation in desired quality.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1116       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1121      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11171122      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.10.  Language Tags</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1118       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1123      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11191124      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A language tag identifies a natural language spoken, written, or</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11201125      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   otherwise conveyed by human beings for communication of information</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    11221127      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP uses language tags within the Accept-Language and Content-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11231128      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Language fields.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1124       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1129      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11251130      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The syntax and registry of HTTP language tags is the same as that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11261131      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   defined by RFC 1766 [RFC1766].  In summary, a language tag is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11271132      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   composed of 1 or more parts: A primary language tag and a possibly</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11281133      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   empty series of subtags:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1129       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1134      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11301135      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">        language-tag  = primary-tag *( "-" subtag )</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11311136      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">        primary-tag   = 1*8ALPHA</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11321137      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">        subtag        = 1*8ALPHA</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1133       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1138      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11341139      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   White space is not allowed within the tag and all tags are case-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11351140      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   insensitive.  The name space of language tags is administered by the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11361141      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   IANA.  Example tags include:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1137       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1142      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11381143      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       en, en-US, en-cockney, i-cherokee, x-pig-latin</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1139       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1144      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11401145      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   where any two-letter primary-tag is an ISO-639 language abbreviation</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11411146      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   and any two-letter initial subtag is an ISO-3166 country code.  (The</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11421147      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   last three tags above are not registered tags; all but the last are</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11431148      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   examples of tags which could be registered in future.)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1144       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1149      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11451150      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.11.  Entity Tags</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1146       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1151      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11471152      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Entity tags are used for comparing two or more entities from the same</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11481153      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   requested resource.  HTTP/1.1 uses entity tags in the ETag</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    11521157      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   in Section 13.3.3.  An entity tag consists of an opaque quoted</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11531158      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   string, possibly prefixed by a weakness indicator.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1154       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1159      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11551160      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      entity-tag = [ weak ] opaque-tag</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11561161      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      weak       = "W/"</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11571162      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      opaque-tag = quoted-string</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1158       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1163      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11591164      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A "strong entity tag" MAY be shared by two entities of a resource</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11601165      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   only if they are equivalent by octet equality.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1161       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1166      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11621167      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A "weak entity tag," indicated by the "W/" prefix, MAY be shared by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11631168      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   two entities of a resource only if the entities are equivalent and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11641169      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   could be substituted for each other with no significant change in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11651170      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   semantics.  A weak entity tag can only be used for weak comparison.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1166       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1171      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11671172      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   An entity tag MUST be unique across all versions of all entities</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11681173      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   associated with a particular resource.  A given entity tag value MAY</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    11711176      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   requests on different URIs does not imply the equivalence of those</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11721177      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entities.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1173       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1178      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11741179      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">3.12.  Range Units</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1175       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1180      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11761181      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP/1.1 allows a client to request that only part (a range of) the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11771182      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response entity be included within the response.  HTTP/1.1 uses range</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    11791184      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   header fields.  An entity can be broken down into subranges according</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11801185      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to various structural units.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1181       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1186      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11821187      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      range-unit       = bytes-unit | other-range-unit</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11831188      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      bytes-unit       = "bytes"</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11841189      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      other-range-unit = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1185       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1190      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11861191      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The only range unit defined by HTTP/1.1 is "bytes".  HTTP/1.1</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11871192      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   implementations MAY ignore ranges specified using other units.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1188       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1193      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11891194      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP/1.1 has been designed to allow implementations of applications</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11901195      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   that do not depend on knowledge of ranges.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1191       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1196      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    11921197      <tr><td class="lineno" valign="top"></td><td class="left">4.  HTTP Message</td><td> </td><td class="right">4.  HTTP Message</td><td class="lineno" valign="top"></td></tr>
    11931198      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12131218      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP header fields, which include general-header (Section 4.5),</td><td> </td><td class="right">   HTTP header fields, which include general-header (Section 4.5),</td><td class="lineno" valign="top"></td></tr>
    12141219      <tr><td><a name="diff0036" /></td></tr>
    1215       <tr><td class="lineno" valign="top"></td><td class="lblock">   request-header (Section <span class="delete">5.3), response-header (Section 6.2), and</span></td><td> </td><td class="rblock">   request-header (Section <span class="insert">4 of [Part2]), response-header (Section 6 of</span></td><td class="lineno" valign="top"></td></tr>
    1216       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">entity-header (Section 7.1) fields, follow the same generic format as</span></td><td> </td><td class="rblock">   <span class="insert">[Part2]), and entity-header (Section 3.1 of [Part3]) fields, follow</span></td><td class="lineno" valign="top"></td></tr>
    1217       <tr><td class="lineno" valign="top"></td><td class="lblock">   th<span class="delete">at given in Section 3.1 of RFC 822 [RFC822].  Each header field</span></td><td> </td><td class="rblock">   th<span class="insert">e same generic format as that given in Section 3.1 of RFC 822</span></td><td class="lineno" valign="top"></td></tr>
    1218       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">consists of a name followed by a colon (":") and the field value.</span></td><td> </td><td class="rblock">   <span class="insert">[RFC822].  Each header field consists of a name followed by a colon</span></td><td class="lineno" valign="top"></td></tr>
    1219       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Field names are case-insensitive.  The field value MAY be preceded by</span></td><td> </td><td class="rblock">   <span class="insert">(":") and the field value.  Field names are case-insensitive.  The</span></td><td class="lineno" valign="top"></td></tr>
    1220       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">any amount of LWS, though a single SP is preferred.  Header fields</span></td><td> </td><td class="rblock">   <span class="insert">field value MAY be preceded by any amount of LWS, though a single SP</span></td><td class="lineno" valign="top"></td></tr>
    1221       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">can be extended over multiple lines by preceding each extra line with</span></td><td> </td><td class="rblock">   <span class="insert">is preferred.  Header fields can be extended over multiple lines by</span></td><td class="lineno" valign="top"></td></tr>
    1222       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">at least one SP or HT.  Applications ought to follow "common form",</span></td><td> </td><td class="rblock">   <span class="insert">preceding each extra line with at least one SP or HT.  Applications</span></td><td class="lineno" valign="top"></td></tr>
    1223       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">where one is known or indicated, when generating HTTP constructs,</span></td><td> </td><td class="rblock">   <span class="insert">ought to follow "common form", where one is known or indicated, when</span></td><td class="lineno" valign="top"></td></tr>
    1224       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">since there might exist some implementations that fail to accept</span></td><td> </td><td class="rblock">   <span class="insert">generating HTTP constructs, since there might exist some</span></td><td class="lineno" valign="top"></td></tr>
    1225       <tr><td class="lineno" valign="top"></td><td class="lblock">   anything beyond the common forms.</td><td> </td><td class="rblock">   <span class="insert">implementations that fail to accept </span>anything beyond the common forms.</td><td class="lineno" valign="top"></td></tr>
     1220      <tr><td class="lineno" valign="top"></td><td class="lblock">   request-header (Section <span class="delete">5.3),</span> response-header (Section <span class="delete">6.2),</span> and</td><td> </td><td class="rblock">   request-header (Section <span class="insert">4 of [Part2]),</span> response-header (Section <span class="insert">6 of</span></td><td class="lineno" valign="top"></td></tr>
     1221      <tr><td class="lineno" valign="top"></td><td class="lblock">   entity-header (Section <span class="delete">7.1)</span> fields, follow the same generic format as</td><td> </td><td class="rblock"><span class="insert">   [Part2]),</span> and entity-header (Section <span class="insert">3.1 of [Part3])</span> fields, follow</td><td class="lineno" valign="top"></td></tr>
     1222      <tr><td class="lineno" valign="top"></td><td class="lblock">   that given in Section 3.1 of RFC 822 [RFC822].  Each header field</td><td> </td><td class="rblock">   the same generic format as that given in Section 3.1 of RFC 822</td><td class="lineno" valign="top"></td></tr>
     1223      <tr><td class="lineno" valign="top"></td><td class="lblock">   consists of a name followed by a colon (":") and the field value.</td><td> </td><td class="rblock">   [RFC822].  Each header field consists of a name followed by a colon</td><td class="lineno" valign="top"></td></tr>
     1224      <tr><td class="lineno" valign="top"></td><td class="lblock">   Field names are case-insensitive.  The field value MAY be preceded by</td><td> </td><td class="rblock">   (":") and the field value.  Field names are case-insensitive.  The</td><td class="lineno" valign="top"></td></tr>
     1225      <tr><td class="lineno" valign="top"></td><td class="lblock">   any amount of LWS, though a single SP is preferred.  Header fields</td><td> </td><td class="rblock">   field value MAY be preceded by any amount of LWS, though a single SP</td><td class="lineno" valign="top"></td></tr>
     1226      <tr><td class="lineno" valign="top"></td><td class="lblock">   can be extended over multiple lines by preceding each extra line with</td><td> </td><td class="rblock">   is preferred.  Header fields can be extended over multiple lines by</td><td class="lineno" valign="top"></td></tr>
     1227      <tr><td class="lineno" valign="top"></td><td class="lblock">   at least one SP or HT.  Applications ought to follow "common form",</td><td> </td><td class="rblock">   preceding each extra line with at least one SP or HT.  Applications</td><td class="lineno" valign="top"></td></tr>
     1228      <tr><td class="lineno" valign="top"></td><td class="lblock">   where one is known or indicated, when generating HTTP constructs,</td><td> </td><td class="rblock">   ought to follow "common form", where one is known or indicated, when</td><td class="lineno" valign="top"></td></tr>
     1229      <tr><td class="lineno" valign="top"></td><td class="lblock">   since there might exist some implementations that fail to accept</td><td> </td><td class="rblock">   generating HTTP constructs, since there might exist some</td><td class="lineno" valign="top"></td></tr>
     1230      <tr><td class="lineno" valign="top"></td><td class="lblock">   anything beyond the common forms.</td><td> </td><td class="rblock">   implementations that fail to accept anything beyond the common forms.</td><td class="lineno" valign="top"></td></tr>
    12261231      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12271232      <tr><td class="lineno" valign="top"></td><td class="left">       message-header = field-name ":" [ field-value ]</td><td> </td><td class="right">       message-header = field-name ":" [ field-value ]</td><td class="lineno" valign="top"></td></tr>
     
    12671272      <tr><td class="lineno" valign="top"></td><td class="left">   the request's message-headers.  A message-body MUST NOT be included</td><td> </td><td class="right">   the request's message-headers.  A message-body MUST NOT be included</td><td class="lineno" valign="top"></td></tr>
    12681273      <tr><td><a name="diff0039" /></td></tr>
    1269       <tr><td class="lineno" valign="top"></td><td class="lblock">   in a request if the specification of the request method</td><td> </td><td class="rblock">   in a request if the specification of the request method<span class="insert"> (Section 3 of</span></td><td class="lineno" valign="top"></td></tr>
    1270       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">(Section 5.1.1) does not allow sending an entity-body in requests.  A</span></td><td> </td><td class="rblock">   <span class="insert">[Part2]) does not allow sending an entity-body in requests.  A server</span></td><td class="lineno" valign="top"></td></tr>
    1271       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">server SHOULD read and forward a message-body on any request; if the</span></td><td> </td><td class="rblock">   <span class="insert">SHOULD read and forward a message-body on any request; if the request</span></td><td class="lineno" valign="top"></td></tr>
    1272       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">request method does not include defined semantics for an entity-body,</span></td><td> </td><td class="rblock">   <span class="insert">method does not include defined semantics for an entity-body, then</span></td><td class="lineno" valign="top"></td></tr>
    1273       <tr><td class="lineno" valign="top"></td><td class="lblock">   the<span class="delete">n the</span> message-body SHOULD be ignored when handling the request.</td><td> </td><td class="rblock">   the message-body SHOULD be ignored when handling the request.</td><td class="lineno" valign="top"></td></tr>
     1274      <tr><td class="lineno" valign="top"></td><td class="lblock">   in a request if the specification of the request method</td><td> </td><td class="rblock">   in a request if the specification of the request method (Section <span class="insert">3 of</span></td><td class="lineno" valign="top"></td></tr>
     1275      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">5.1.1)</span> does not allow sending an entity-body in requests.  A</td><td> </td><td class="rblock"><span class="insert">   [Part2])</span> does not allow sending an entity-body in requests.  A server</td><td class="lineno" valign="top"></td></tr>
     1276      <tr><td class="lineno" valign="top"></td><td class="lblock">   server SHOULD read and forward a message-body on any request; if the</td><td> </td><td class="rblock">   SHOULD read and forward a message-body on any request; if the request</td><td class="lineno" valign="top"></td></tr>
     1277      <tr><td class="lineno" valign="top"></td><td class="lblock">   request method does not include defined semantics for an entity-body,</td><td> </td><td class="rblock">   method does not include defined semantics for an entity-body, then</td><td class="lineno" valign="top"></td></tr>
     1278      <tr><td class="lineno" valign="top"></td><td class="lblock">   then the message-body SHOULD be ignored when handling the request.</td><td> </td><td class="rblock">   the message-body SHOULD be ignored when handling the request.</td><td class="lineno" valign="top"></td></tr>
    12741279      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12751280      <tr><td class="lineno" valign="top"></td><td class="left">   For response messages, whether or not a message-body is included with</td><td> </td><td class="right">   For response messages, whether or not a message-body is included with</td><td class="lineno" valign="top"></td></tr>
     
    12951300      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12961301      <tr><td><a name="diff0040" /></td></tr>
    1297       <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  If a Transfer-Encoding header field (Section <span class="delete">14.41) is present</span></td><td> </td><td class="rblock">   2.  If a Transfer-Encoding header field (Section <span class="insert">8.7) is present and</span></td><td class="lineno" valign="top"></td></tr>
    1298       <tr><td class="lineno" valign="top"></td><td class="lblock">       <span class="delete">and has any value other than "identity", then the transfer-length</span></td><td> </td><td class="rblock">       <span class="insert">has any value other than "identity", then the transfer-length is</span></td><td class="lineno" valign="top"></td></tr>
    1299       <tr><td class="lineno" valign="top"></td><td class="lblock">       <span class="delete">is defined by use of the "chunked" transfer-coding (Section 3.6</span>),</td><td> </td><td class="rblock">       <span class="insert">defined by use of the "chunked" transfer-coding (Section 3.4</span>),</td><td class="lineno" valign="top"></td></tr>
     1302      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  If a Transfer-Encoding header field (Section <span class="delete">14.41)</span> is present</td><td> </td><td class="rblock">   2.  If a Transfer-Encoding header field (Section <span class="insert">8.7)</span> is present and</td><td class="lineno" valign="top"></td></tr>
     1303      <tr><td class="lineno" valign="top"></td><td class="lblock">       and has any value other than "identity", then the transfer-length</td><td> </td><td class="rblock">       has any value other than "identity", then the transfer-length is</td><td class="lineno" valign="top"></td></tr>
     1304      <tr><td class="lineno" valign="top"></td><td class="lblock">       is defined by use of the "chunked" transfer-coding (Section <span class="delete">3.6),</span></td><td> </td><td class="rblock">       defined by use of the "chunked" transfer-coding (Section <span class="insert">3.4),</span></td><td class="lineno" valign="top"></td></tr>
    13001305      <tr><td class="lineno" valign="top"></td><td class="left">       unless the message is terminated by closing the connection.</td><td> </td><td class="right">       unless the message is terminated by closing the connection.</td><td class="lineno" valign="top"></td></tr>
    13011306      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    13461351      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    13471352      <tr><td><a name="diff0043" /></td></tr>
    1348       <tr><td class="lineno" valign="top"></td><td class="lblock">       general-header = Cache-Control            ; <span class="delete">Section 14.9</span></td><td> </td><td class="rblock">       general-header = Cache-Control            ; <span class="insert">[Part6], Section 3.2</span></td><td class="lineno" valign="top"></td></tr>
     1353      <tr><td class="lineno" valign="top"></td><td class="lblock">       general-header = Cache-Control            ; Section <span class="delete">14.9</span></td><td> </td><td class="rblock">       general-header = Cache-Control            ; <span class="insert">[Part6],</span> Section <span class="insert">3.2</span></td><td class="lineno" valign="top"></td></tr>
    13491354      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Connection               ; Section <span class="delete">14.10</span></td><td> </td><td class="rblock">                      | Connection               ; Section <span class="insert">8.1</span></td><td class="lineno" valign="top"></td></tr>
    13501355      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Date                     ; Section <span class="delete">14.18</span></td><td> </td><td class="rblock">                      | Date                     ; Section <span class="insert">8.3</span></td><td class="lineno" valign="top"></td></tr>
    1351       <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Pragma                   ; <span class="delete">Section 14.32</span></td><td> </td><td class="rblock">                      | Pragma                   ; <span class="insert">[Part6], Section 3.4</span></td><td class="lineno" valign="top"></td></tr>
     1356      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Pragma                   ; Section <span class="delete">14.32</span></td><td> </td><td class="rblock">                      | Pragma                   ; <span class="insert">[Part6],</span> Section <span class="insert">3.4</span></td><td class="lineno" valign="top"></td></tr>
    13521357      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Trailer                  ; Section <span class="delete">14.40</span></td><td> </td><td class="rblock">                      | Trailer                  ; Section <span class="insert">8.6</span></td><td class="lineno" valign="top"></td></tr>
    13531358      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Transfer-Encoding        ; Section <span class="delete">14.41</span></td><td> </td><td class="rblock">                      | Transfer-Encoding        ; Section <span class="insert">8.7</span></td><td class="lineno" valign="top"></td></tr>
    13541359      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Upgrade                  ; Section <span class="delete">14.42</span></td><td> </td><td class="rblock">                      | Upgrade                  ; Section <span class="insert">8.8</span></td><td class="lineno" valign="top"></td></tr>
    13551360      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Via                      ; Section <span class="delete">14.45</span></td><td> </td><td class="rblock">                      | Via                      ; Section <span class="insert">8.9</span></td><td class="lineno" valign="top"></td></tr>
    1356       <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Warning                  ; <span class="delete">Section 14.4</span>6</td><td> </td><td class="rblock">                      | Warning                  ; <span class="insert">[Part6], Section 3.</span>6</td><td class="lineno" valign="top"></td></tr>
     1361      <tr><td class="lineno" valign="top"></td><td class="lblock">                      | Warning                  ; Section <span class="delete">14.46</span></td><td> </td><td class="rblock">                      | Warning                  ; <span class="insert">[Part6],</span> Section <span class="insert">3.6</span></td><td class="lineno" valign="top"></td></tr>
    13571362      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    13581363      <tr><td class="lineno" valign="top"></td><td class="left">   General-header field names can be extended reliably only in</td><td> </td><td class="right">   General-header field names can be extended reliably only in</td><td class="lineno" valign="top"></td></tr>
     
    13721377      <tr><td class="lineno" valign="top"></td><td class="left">                        *(( general-header        ; Section 4.5</td><td> </td><td class="right">                        *(( general-header        ; Section 4.5</td><td class="lineno" valign="top"></td></tr>
    13731378      <tr><td><a name="diff0044" /></td></tr>
    1374       <tr><td class="lineno" valign="top"></td><td class="lblock">                         | request-header         ; <span class="delete">Section 5.3</span></td><td> </td><td class="rblock">                         | request-header         ; <span class="insert">[Part2], Section 4</span></td><td class="lineno" valign="top"></td></tr>
    1375       <tr><td class="lineno" valign="top"></td><td class="lblock">                         | entity-header ) CRLF)  ; <span class="delete">Section 7</span>.1</td><td> </td><td class="rblock">                         | entity-header ) CRLF)  ; <span class="insert">[Part3], Section 3</span>.1</td><td class="lineno" valign="top"></td></tr>
     1379      <tr><td class="lineno" valign="top"></td><td class="lblock">                         | request-header         ; Section <span class="delete">5.3</span></td><td> </td><td class="rblock">                         | request-header         ; <span class="insert">[Part2],</span> Section <span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
     1380      <tr><td class="lineno" valign="top"></td><td class="lblock">                         | entity-header ) CRLF)  ; Section <span class="delete">7.1</span></td><td> </td><td class="rblock">                         | entity-header ) CRLF)  ; <span class="insert">[Part3],</span> Section <span class="insert">3.1</span></td><td class="lineno" valign="top"></td></tr>
    13761381      <tr><td class="lineno" valign="top"></td><td class="left">                        CRLF</td><td> </td><td class="right">                        CRLF</td><td class="lineno" valign="top"></td></tr>
    13771382      <tr><td class="lineno" valign="top"></td><td class="left">                        [ message-body ]          ; Section 4.3</td><td> </td><td class="right">                        [ message-body ]          ; Section 4.3</td><td class="lineno" valign="top"></td></tr>
     
    13921397      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    13931398      <tr><td><a name="diff0045" /></td></tr>
    1394       <tr><td class="lineno" valign="top"></td><td class="lblock">       Method         = <span class="delete">"OPTIONS"                ; Section 9.2</span></td><td> </td><td class="rblock">       Method         = <span class="insert">token</span></td><td class="lineno" valign="top"></td></tr>
     1399      <tr><td class="lineno" valign="top"></td><td class="lblock">       Method         = <span class="delete">"OPTIONS"                ; Section 9.2</span></td><td> </td><td class="rblock">       Method         = token</td><td class="lineno" valign="top"></td></tr>
    13951400      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | "GET"                    ; Section 9.3</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    13961401      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | "HEAD"                   ; Section 9.4</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    14011406      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | "CONNECT"                ; Section 9.9</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14021407      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | extension-method</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1403       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       extension-method = token</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1404       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1405       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The list of methods allowed by a resource can be specified in an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1408      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       extension-method =</span> token</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1409      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1410      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">The list of methods allowed by a resource can be specified in an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14061411      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Allow header field (Section 14.7).  The return code of the response</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14071412      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   always notifies the client whether a method is currently allowed on a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    14881493      <tr><td><a name="diff0048" /></td></tr>
    14891494      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">5.3.  Request Header Fields</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1490       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1495      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14911496      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The request-header fields allow the client to pass additional</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14921497      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   information about the request, and about the client itself, to the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    14941499      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   equivalent to the parameters on a programming language method</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14951500      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   invocation.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1496       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1501      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14971502      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       request-header = Accept                   ; Section 14.1</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    14981503      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | Accept-Charset           ; Section 14.2</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    15141519      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | TE                       ; Section 14.39</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15151520      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | User-Agent               ; Section 14.43</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1516       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1521      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15171522      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Request-header field names can be extended reliably only in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15181523      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   combination with a change in the protocol version.  However, new or</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    15211526      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   be request-header fields.  Unrecognized header fields are treated as</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15221527      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity-header fields.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1523       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1528      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15241529      <tr><td class="lineno" valign="top"></td><td class="left">6.  Response</td><td> </td><td class="right">6.  Response</td><td class="lineno" valign="top"></td></tr>
    15251530      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    15301535      <tr><td class="lineno" valign="top"></td><td class="left">                       *(( general-header        ; Section 4.5</td><td> </td><td class="right">                       *(( general-header        ; Section 4.5</td><td class="lineno" valign="top"></td></tr>
    15311536      <tr><td><a name="diff0049" /></td></tr>
    1532       <tr><td class="lineno" valign="top"></td><td class="lblock">                        | response-header        ; <span class="delete">Section 6.2</span></td><td> </td><td class="rblock">                        | response-header        ; <span class="insert">[Part2], Section 6</span></td><td class="lineno" valign="top"></td></tr>
    1533       <tr><td class="lineno" valign="top"></td><td class="lblock">                        | entity-header ) CRLF)  ; <span class="delete">Section 7</span>.1</td><td> </td><td class="rblock">                        | entity-header ) CRLF)  ; <span class="insert">[Part3], Section 3</span>.1</td><td class="lineno" valign="top"></td></tr>
     1537      <tr><td class="lineno" valign="top"></td><td class="lblock">                        | response-header        ; Section <span class="delete">6.2</span></td><td> </td><td class="rblock">                        | response-header        ; <span class="insert">[Part2],</span> Section <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
     1538      <tr><td class="lineno" valign="top"></td><td class="lblock">                        | entity-header ) CRLF)  ; Section <span class="delete">7.1</span></td><td> </td><td class="rblock">                        | entity-header ) CRLF)  ; <span class="insert">[Part3],</span> Section <span class="insert">3.1</span></td><td class="lineno" valign="top"></td></tr>
    15341539      <tr><td class="lineno" valign="top"></td><td class="left">                       CRLF</td><td> </td><td class="right">                       CRLF</td><td class="lineno" valign="top"></td></tr>
    15351540      <tr><td><a name="diff0050" /></td></tr>
     
    15511556      <tr><td class="lineno" valign="top"></td><td class="left">   attempt to understand and satisfy the request.  These codes are fully</td><td> </td><td class="right">   attempt to understand and satisfy the request.  These codes are fully</td><td class="lineno" valign="top"></td></tr>
    15521557      <tr><td><a name="diff0051" /></td></tr>
    1553       <tr><td class="lineno" valign="top"></td><td class="lblock">   defined in Section <span class="delete">10.  The Reason-Phrase is intended to give a short</span></td><td> </td><td class="rblock">   defined in Section <span class="insert">9 of [Part2].  The Reason-Phrase is intended to</span></td><td class="lineno" valign="top"></td></tr>
    1554       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">textual description of the Status-Code.  The Status-Code is intended</span></td><td> </td><td class="rblock">   <span class="insert">give a short textual description of the Status-Code.  The Status-Code</span></td><td class="lineno" valign="top"></td></tr>
    1555       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">for use by automata and the Reason-Phrase is intended for the human</span></td><td> </td><td class="rblock">   <span class="insert">is intended for use by automata and the Reason-Phrase is intended for</span></td><td class="lineno" valign="top"></td></tr>
    1556       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">user.  The client is not required to examine or display the Reason-</span></td><td> </td><td class="rblock">   <span class="insert">the human user.  The client is not required to examine or display the</span></td><td class="lineno" valign="top"></td></tr>
    1557       <tr><td class="lineno" valign="top"></td><td class="lblock">   Phrase.</td><td> </td><td class="rblock">   <span class="insert">Reason-</span>Phrase.</td><td class="lineno" valign="top"></td></tr>
     1558      <tr><td class="lineno" valign="top"></td><td class="lblock">   defined in Section <span class="delete">10.</span>  The Reason-Phrase is intended to give a short</td><td> </td><td class="rblock">   defined in Section <span class="insert">9 of [Part2].</span>  The Reason-Phrase is intended to</td><td class="lineno" valign="top"></td></tr>
     1559      <tr><td class="lineno" valign="top"></td><td class="lblock">   textual description of the Status-Code.  The Status-Code is intended</td><td> </td><td class="rblock">   give a short textual description of the Status-Code.  The Status-Code</td><td class="lineno" valign="top"></td></tr>
     1560      <tr><td class="lineno" valign="top"></td><td class="lblock">   for use by automata and the Reason-Phrase is intended for the human</td><td> </td><td class="rblock">   is intended for use by automata and the Reason-Phrase is intended for</td><td class="lineno" valign="top"></td></tr>
     1561      <tr><td class="lineno" valign="top"></td><td class="lblock">   user.  The client is not required to examine or display the <span class="delete">Reason-</span></td><td> </td><td class="rblock">   the human user.  The client is not required to examine or display the</td><td class="lineno" valign="top"></td></tr>
     1562      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Phrase.</span></td><td> </td><td class="rblock">   <span class="insert">Reason-Phrase.</span></td><td class="lineno" valign="top"></td></tr>
    15581563      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    15591564      <tr><td class="lineno" valign="top"></td><td class="left">   The first digit of the Status-Code defines the class of response.</td><td> </td><td class="right">   The first digit of the Status-Code defines the class of response.</td><td class="lineno" valign="top"></td></tr>
     
    15761581      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    15771582      <tr><td><a name="diff0052" /></td></tr>
    1578       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">The individual values of the numeric status codes defined for</span></td><td> </td><td class="rblock">   <span class="insert">   Status-Code    = 3DIGIT</span></td><td class="lineno" valign="top"></td></tr>
     1583      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">The individual values of the numeric status codes defined for</span></td><td> </td><td class="rblock">      Status-Code    = 3DIGIT</td><td class="lineno" valign="top"></td></tr>
    15791584      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP/1.1, and an example set of corresponding Reason-Phrase's, are</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15801585      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   presented below.  The reason phrases listed here are only</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15811586      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   recommendations -- they MAY be replaced by local equivalents without</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15821587      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   affecting the protocol.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1583       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1584       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Status-Code    =</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1585       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">            "100"  ; Section 10.1.1: Continue</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1588      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1589      <tr><td class="lineno" valign="top"></td><td class="lblock">      Status-Code    =</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1590      <tr><td class="lineno" valign="top"></td><td class="lblock">            <span class="delete">"100"  ; Section 10.1.1: Continue</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15861591      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">          | "101"  ; Section 10.1.2: Switching Protocols</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    15871592      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">          | "200"  ; Section 10.2.1: OK</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    16241629      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">          | "505"  ; Section 10.5.6: HTTP Version not supported</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16251630      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">          | extension-code</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1626       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1627       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      extension-code = 3DIGIT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1631      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1632      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      extension-code =</span> 3DIGIT</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16281633      <tr><td class="lineno" valign="top"></td><td class="left">      Reason-Phrase  = *&lt;TEXT, excluding CR, LF&gt;</td><td> </td><td class="right">      Reason-Phrase  = *&lt;TEXT, excluding CR, LF&gt;</td><td class="lineno" valign="top"></td></tr>
    16291634      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    16301635      <tr><td><a name="diff0053" /></td></tr>
    1631       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP status codes are extensible.  HTTP applications are not required</span></td><td> </td><td class="rblock"><span class="insert">7.  Connections</span></td><td class="lineno" valign="top"></td></tr>
     1636      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">HTTP status codes are extensible.  HTTP applications are not required</span></td><td> </td><td class="rblock">7.  Connections</td><td class="lineno" valign="top"></td></tr>
    16321637      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to understand the meaning of all registered status codes, though such</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16331638      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   understanding is obviously desirable.  However, applications MUST</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    16421647      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   with the response, since that entity is likely to include human-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16431648      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   readable information which will explain the unusual status.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1644       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1649      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16451650      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">6.2.  Response Header Fields</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1646       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1651      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16471652      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The response-header fields allow the server to pass additional</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16481653      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   information about the response which cannot be placed in the Status-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16491654      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Line.  These header fields give information about the server and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16501655      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   about further access to the resource identified by the Request-URI.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1651       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1656      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16521657      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       response-header = Accept-Ranges           ; Section 14.5</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16531658      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                       | Age                     ; Section 14.6</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    16591664      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                       | Vary                    ; Section 14.44</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16601665      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                       | WWW-Authenticate        ; Section 14.47</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1661       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1666      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16621667      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Response-header field names can be extended reliably only in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16631668      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   combination with a change in the protocol version.  However, new or</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    16661671      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   be response-header fields.  Unrecognized header fields are treated as</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16671672      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity-header fields.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1668       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1669       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">7.  Entity</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1670       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1673      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1674      <tr><td class="lineno" valign="top"></td><td class="lblock">7.  <span class="delete">Entity</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1675      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16711676      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Request and Response messages MAY transfer an entity if not otherwise</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16721677      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   restricted by the request method or response status code.  An entity</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16731678      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   consists of entity-header fields and an entity-body, although some</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16741679      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   responses will only include the entity-headers.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1675       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1680      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16761681      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   In this section, both sender and recipient refer to either the client</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16771682      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   or the server, depending on who sends and who receives the entity.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1678       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1683      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16791684      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">7.1.  Entity Header Fields</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1680       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1685      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16811686      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Entity-header fields define metainformation about the entity-body or,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16821687      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   if no body is present, about the resource identified by the request.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16831688      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Some of this metainformation is OPTIONAL; some might be REQUIRED by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16841689      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   portions of this specification.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1685       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1690      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16861691      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       entity-header  = Allow                    ; Section 14.7</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16871692      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | Content-Encoding         ; Section 14.11</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    16951700      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | Last-Modified            ; Section 14.29</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16961701      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                      | extension-header</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1697       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1702      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16981703      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       extension-header = message-header</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1699       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1704      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17001705      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The extension-header mechanism allows additional entity-header fields</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17011706      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to be defined without changing the protocol, but these fields cannot</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    17031708      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   fields SHOULD be ignored by the recipient and MUST be forwarded by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17041709      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   transparent proxies.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1705       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1710      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17061711      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">7.2.  Entity Body</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1707       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1712      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17081713      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The entity-body (if any) sent with an HTTP request or response is in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17091714      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   a format and encoding defined by the entity-header fields.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1710       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1715      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17111716      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       entity-body    = *OCTET</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1712       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1717      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17131718      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   An entity-body is only present in a message when a message-body is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17141719      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   present, as described in Section 4.3.  The entity-body is obtained</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17151720      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   from the message-body by decoding any Transfer-Encoding that might</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17161721      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   have been applied to ensure safe and proper transfer of the message.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1717       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1722      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17181723      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">7.2.1.  Type</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1719       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1724      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17201725      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   When an entity-body is included with a message, the data type of that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17211726      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   body is determined via the header fields Content-Type and Content-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17221727      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Encoding.  These define a two-layer, ordered encoding model:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1723       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1728      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17241729      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       entity-body := Content-Encoding( Content-Type( data ) )</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1725       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1730      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17261731      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Content-Type specifies the media type of the underlying data.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1727       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1732      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17281733      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Content-Encoding may be used to indicate any additional content</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17291734      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   codings applied to the data, usually for the purpose of data</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17301735      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   compression, that are a property of the requested resource.  There is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17311736      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   no default encoding.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1732       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1737      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17331738      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Any HTTP/1.1 message containing an entity-body SHOULD include a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17341739      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Content-Type header field defining the media type of that body.  If</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    17381743      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   resource.  If the media type remains unknown, the recipient SHOULD</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17391744      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   treat it as type "application/octet-stream".</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1740       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1745      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17411746      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">7.2.2.  Entity Length</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1742       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1747      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17431748      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The entity-length of a message is the length of the message-body</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17441749      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   before any transfer-codings have been applied.  Section 4.4 defines</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17451750      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   how the transfer-length of a message-body is determined.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1746       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1747       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">8.  Connections</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1751      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1752      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">8.</span>  Connections</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17481753      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    17491754      <tr><td><a name="diff0054" /></td></tr>
     
    17861791      <tr><td class="lineno" valign="top"></td><td class="left">   server can signal the close of a TCP connection.  This signaling</td><td> </td><td class="right">   server can signal the close of a TCP connection.  This signaling</td><td class="lineno" valign="top"></td></tr>
    17871792      <tr><td><a name="diff0057" /></td></tr>
    1788       <tr><td class="lineno" valign="top"></td><td class="lblock">   takes place using the Connection header field (Section <span class="delete">14.10).  Once</span></td><td> </td><td class="rblock">   takes place using the Connection header field (Section <span class="insert">8.1).  Once a</span></td><td class="lineno" valign="top"></td></tr>
    1789       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">a </span>close has been signaled, the client MUST NOT send any more requests</td><td> </td><td class="rblock">   close has been signaled, the client MUST NOT send any more requests</td><td class="lineno" valign="top"></td></tr>
     1793      <tr><td class="lineno" valign="top"></td><td class="lblock">   takes place using the Connection header field (Section <span class="delete">14.10).</span>  Once</td><td> </td><td class="rblock">   takes place using the Connection header field (Section <span class="insert">8.1).</span>  Once a</td><td class="lineno" valign="top"></td></tr>
     1794      <tr><td class="lineno" valign="top"></td><td class="lblock">   a close has been signaled, the client MUST NOT send any more requests</td><td> </td><td class="rblock">   close has been signaled, the client MUST NOT send any more requests</td><td class="lineno" valign="top"></td></tr>
    17901795      <tr><td class="lineno" valign="top"></td><td class="left">   on that connection.</td><td> </td><td class="right">   on that connection.</td><td class="lineno" valign="top"></td></tr>
    17911796      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    18401845      <tr><td class="lineno" valign="top"></td><td class="left">   Clients SHOULD NOT pipeline requests using non-idempotent methods or</td><td> </td><td class="right">   Clients SHOULD NOT pipeline requests using non-idempotent methods or</td><td class="lineno" valign="top"></td></tr>
    18411846      <tr><td><a name="diff0061" /></td></tr>
    1842       <tr><td class="lineno" valign="top"></td><td class="lblock">   non-idempotent sequences of methods (see Section <span class="delete">9.1.2).  Otherwise,</span></td><td> </td><td class="rblock">   non-idempotent sequences of methods (see Section <span class="insert">8.1.2 of [Part2]).</span></td><td class="lineno" valign="top"></td></tr>
    1843       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">a premature termination of the transport connection could lead to</span></td><td> </td><td class="rblock">   <span class="insert">Otherwise, a premature termination of the transport connection could</span></td><td class="lineno" valign="top"></td></tr>
    1844       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">indeterminate results.  A client wishing to send a non-idempotent</span></td><td> </td><td class="rblock">   <span class="insert">lead to indeterminate results.  A client wishing to send a non-</span></td><td class="lineno" valign="top"></td></tr>
    1845       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">request SHOULD wait to send that request until it has received the</span></td><td> </td><td class="rblock">   <span class="insert">idempotent request SHOULD wait to send that request until it has</span></td><td class="lineno" valign="top"></td></tr>
    1846       <tr><td class="lineno" valign="top"></td><td class="lblock">   response status for the previous request.</td><td> </td><td class="rblock">   re<span class="insert">ceived the re</span>sponse status for the previous request.</td><td class="lineno" valign="top"></td></tr>
     1847      <tr><td class="lineno" valign="top"></td><td class="lblock">   non-idempotent sequences of methods (see Section <span class="delete">9.1.2).</span>  Otherwise,</td><td> </td><td class="rblock">   non-idempotent sequences of methods (see Section <span class="insert">8.1.2 of [Part2]).</span></td><td class="lineno" valign="top"></td></tr>
     1848      <tr><td class="lineno" valign="top"></td><td class="lblock">   a premature termination of the transport connection could lead to</td><td> </td><td class="rblock">   Otherwise, a premature termination of the transport connection could</td><td class="lineno" valign="top"></td></tr>
     1849      <tr><td class="lineno" valign="top"></td><td class="lblock">   indeterminate results.  A client wishing to send a <span class="delete">non-idempotent</span></td><td> </td><td class="rblock">   lead to indeterminate results.  A client wishing to send a <span class="insert">non-</span></td><td class="lineno" valign="top"></td></tr>
     1850      <tr><td class="lineno" valign="top"></td><td class="lblock">   request SHOULD wait to send that request until it has received the</td><td> </td><td class="rblock"><span class="insert">   idempotent</span> request SHOULD wait to send that request until it has</td><td class="lineno" valign="top"></td></tr>
     1851      <tr><td class="lineno" valign="top"></td><td class="lblock">   response status for the previous request.</td><td> </td><td class="rblock">   received the response status for the previous request.</td><td class="lineno" valign="top"></td></tr>
    18471852      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    18481853      <tr><td><a name="diff0062" /></td></tr>
     
    18891894      <tr><td class="lineno" valign="top"></td><td class="left">   without user interaction so long as the request sequence is</td><td> </td><td class="right">   without user interaction so long as the request sequence is</td><td class="lineno" valign="top"></td></tr>
    18901895      <tr><td><a name="diff0065" /></td></tr>
    1891       <tr><td class="lineno" valign="top"></td><td class="lblock">   idempotent (see Section <span class="delete">9.1.2).  Non-idempotent methods or sequences</span></td><td> </td><td class="rblock">   idempotent (see Section <span class="insert">8.1.2 of [Part2]).  Non-idempotent methods or</span></td><td class="lineno" valign="top"></td></tr>
    1892       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">MUST NOT be automatically retried, although user agents MAY offer a</span></td><td> </td><td class="rblock">   <span class="insert">sequences MUST NOT be automatically retried, although user agents MAY</span></td><td class="lineno" valign="top"></td></tr>
    1893       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">human operator the choice of retrying the request(s).  Confirmation</span></td><td> </td><td class="rblock">   <span class="insert">offer a human operator the choice of retrying the request(s).</span></td><td class="lineno" valign="top"></td></tr>
    1894       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">by user-agent software with semantic understanding of the application</span></td><td> </td><td class="rblock">   <span class="insert">Confirmation by user-agent software with semantic understanding of</span></td><td class="lineno" valign="top"></td></tr>
    1895       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">MAY substitute for user confirmation.  The automatic retry SHOULD NOT</span></td><td> </td><td class="rblock">   <span class="insert">the application MAY substitute for user confirmation.  The automatic</span></td><td class="lineno" valign="top"></td></tr>
    1896       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">be repeated if the second sequence of requests fails.</span></td><td> </td><td class="rblock">   <span class="insert">retry SHOULD NOT be repeated if the second sequence of requests</span></td><td class="lineno" valign="top"></td></tr>
    1897       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   fails.</span></td><td class="lineno" valign="top"></td></tr>
     1896      <tr><td class="lineno" valign="top"></td><td class="lblock">   idempotent (see Section <span class="delete">9.1.2).</span>  Non-idempotent methods or sequences</td><td> </td><td class="rblock">   idempotent (see Section <span class="insert">8.1.2 of [Part2]).</span>  Non-idempotent methods or</td><td class="lineno" valign="top"></td></tr>
     1897      <tr><td class="lineno" valign="top"></td><td class="lblock">   MUST NOT be automatically retried, although user agents MAY offer a</td><td> </td><td class="rblock">   sequences MUST NOT be automatically retried, although user agents MAY</td><td class="lineno" valign="top"></td></tr>
     1898      <tr><td class="lineno" valign="top"></td><td class="lblock">   human operator the choice of retrying the request(s).  Confirmation</td><td> </td><td class="rblock">   offer a human operator the choice of retrying the request(s).</td><td class="lineno" valign="top"></td></tr>
     1899      <tr><td class="lineno" valign="top"></td><td class="lblock">   by user-agent software with semantic understanding of the application</td><td> </td><td class="rblock">   Confirmation by user-agent software with semantic understanding of</td><td class="lineno" valign="top"></td></tr>
     1900      <tr><td class="lineno" valign="top"></td><td class="lblock">   MAY substitute for user confirmation.  The automatic retry SHOULD NOT</td><td> </td><td class="rblock">   the application MAY substitute for user confirmation.  The automatic</td><td class="lineno" valign="top"></td></tr>
     1901      <tr><td class="lineno" valign="top"></td><td class="lblock">   be repeated if the second sequence of requests fails.</td><td> </td><td class="rblock">   retry SHOULD NOT be repeated if the second sequence of requests</td><td class="lineno" valign="top"></td></tr>
     1902      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   fails.</td><td class="lineno" valign="top"></td></tr>
    18981903      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    18991904      <tr><td class="lineno" valign="top"></td><td class="left">   Servers SHOULD always respond to at least one request per connection,</td><td> </td><td class="right">   Servers SHOULD always respond to at least one request per connection,</td><td class="lineno" valign="top"></td></tr>
     
    19381943      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19391944      <tr><td><a name="diff0071" /></td></tr>
    1940       <tr><td class="lineno" valign="top"></td><td class="lblock">   The purpose of the 100 (Continue) status (see Section <span class="delete">10.1.1) is to</span></td><td> </td><td class="rblock">   The purpose of the 100 (Continue) status (see Section <span class="insert">9.1.1 of</span></td><td class="lineno" valign="top"></td></tr>
    1941       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">allow a client that is sending a request message with a request body</span></td><td> </td><td class="rblock">   <span class="insert">[Part2]) is to allow a client that is sending a request message with</span></td><td class="lineno" valign="top"></td></tr>
    1942       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">to determine if the origin server is willing to accept the reques</span>t</td><td> </td><td class="rblock">   <span class="insert">a request body to determine if the origin server is willing to accep</span>t</td><td class="lineno" valign="top"></td></tr>
    1943       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">(based on the request headers) before the client sends the request</span></td><td> </td><td class="rblock">   <span class="insert">the request (based on the request headers) before the client sends</span></td><td class="lineno" valign="top"></td></tr>
    1944       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">body.  In some cases, it might either be inappropriate or highly</span></td><td> </td><td class="rblock">   <span class="insert">the request body.  In some cases, it might either be inappropriate or</span></td><td class="lineno" valign="top"></td></tr>
    1945       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">inefficient for the client to send the body if the server will reject</span></td><td> </td><td class="rblock">   <span class="insert">highly inefficient for the client to send the body if the server will</span></td><td class="lineno" valign="top"></td></tr>
    1946       <tr><td class="lineno" valign="top"></td><td class="lblock">   the message without looking at the body.</td><td> </td><td class="rblock">   <span class="insert">reject </span>the message without looking at the body.</td><td class="lineno" valign="top"></td></tr>
     1945      <tr><td class="lineno" valign="top"></td><td class="lblock">   The purpose of the 100 (Continue) status (see Section <span class="delete">10.1.1)</span> is to</td><td> </td><td class="rblock">   The purpose of the 100 (Continue) status (see Section <span class="insert">9.1.1 of</span></td><td class="lineno" valign="top"></td></tr>
     1946      <tr><td class="lineno" valign="top"></td><td class="lblock">   allow a client that is sending a request message with a request body</td><td> </td><td class="rblock"><span class="insert">   [Part2])</span> is to allow a client that is sending a request message with</td><td class="lineno" valign="top"></td></tr>
     1947      <tr><td class="lineno" valign="top"></td><td class="lblock">   to determine if the origin server is willing to accept the request</td><td> </td><td class="rblock">   a request body to determine if the origin server is willing to accept</td><td class="lineno" valign="top"></td></tr>
     1948      <tr><td class="lineno" valign="top"></td><td class="lblock">   (based on the request headers) before the client sends the request</td><td> </td><td class="rblock">   the request (based on the request headers) before the client sends</td><td class="lineno" valign="top"></td></tr>
     1949      <tr><td class="lineno" valign="top"></td><td class="lblock">   body.  In some cases, it might either be inappropriate or highly</td><td> </td><td class="rblock">   the request body.  In some cases, it might either be inappropriate or</td><td class="lineno" valign="top"></td></tr>
     1950      <tr><td class="lineno" valign="top"></td><td class="lblock">   inefficient for the client to send the body if the server will reject</td><td> </td><td class="rblock">   highly inefficient for the client to send the body if the server will</td><td class="lineno" valign="top"></td></tr>
     1951      <tr><td class="lineno" valign="top"></td><td class="lblock">   the message without looking at the body.</td><td> </td><td class="rblock">   reject the message without looking at the body.</td><td class="lineno" valign="top"></td></tr>
    19471952      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19481953      <tr><td class="lineno" valign="top"></td><td class="left">   Requirements for HTTP/1.1 clients:</td><td> </td><td class="right">   Requirements for HTTP/1.1 clients:</td><td class="lineno" valign="top"></td></tr>
     
    19541959      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19551960      <tr><td><a name="diff0073" /></td></tr>
    1956       <tr><td class="lineno" valign="top"></td><td class="lblock">   o  A client MUST NOT send an Expect request-header field</td><td> </td><td class="rblock">   o  A client MUST NOT send an Expect request-header field<span class="insert"> (Section</span></td><td class="lineno" valign="top"></td></tr>
    1957       <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">(Section 14.20) with the "100-continue" expectation if it does not</span></td><td> </td><td class="rblock">      <span class="insert">10.2 of [Part2]) with the "100-continue" expectation if it does</span></td><td class="lineno" valign="top"></td></tr>
    1958       <tr><td class="lineno" valign="top"></td><td class="lblock">      intend to send a request body.</td><td> </td><td class="rblock">      <span class="insert">not </span>intend to send a request body.</td><td class="lineno" valign="top"></td></tr>
     1961      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  A client MUST NOT send an Expect request-header field</td><td> </td><td class="rblock">   o  A client MUST NOT send an Expect request-header field (Section</td><td class="lineno" valign="top"></td></tr>
     1962      <tr><td class="lineno" valign="top"></td><td class="lblock">      (Section <span class="delete">14.20)</span> with the "100-continue" expectation if it does not</td><td> </td><td class="rblock">      <span class="insert">10.2 of [Part2])</span> with the "100-continue" expectation if it does</td><td class="lineno" valign="top"></td></tr>
     1963      <tr><td class="lineno" valign="top"></td><td class="lblock">      intend to send a request body.</td><td> </td><td class="rblock">      not intend to send a request body.</td><td class="lineno" valign="top"></td></tr>
    19591964      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19601965      <tr><td class="lineno" valign="top"></td><td class="left">   Because of the presence of older implementations, the protocol allows</td><td> </td><td class="right">   Because of the presence of older implementations, the protocol allows</td><td class="lineno" valign="top"></td></tr>
     
    20072012      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20082013      <tr><td><a name="diff0076" /></td></tr>
    2009       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.  Metho</span>d Definitions</td><td> </td><td class="rblock"><span class="insert">8.  Header Fiel</span>d Definitions</td><td class="lineno" valign="top"></td></tr>
    2010       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2014      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.  Method Definitions</span></td><td> </td><td class="rblock"><span class="insert">8.</span>  Header Field Definitions</td><td class="lineno" valign="top"></td></tr>
     2015      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20112016      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The set of common methods for HTTP/1.1 is defined below.  Although</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20122017      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   this set can be expanded, additional methods cannot be assumed to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20142019      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The Host request-header field (Section 14.23) MUST accompany all</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20152020      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP/1.1 requests.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2016       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2021      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20172022      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.1.  Safe and Idempotent Methods</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2018       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2023      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20192024      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.1.1.  Safe Methods</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2020       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2025      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20212026      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Implementors should be aware that the software represents the user in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20222027      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   their interactions over the Internet, and should be careful to allow</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20232028      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the user to be aware of any actions they might take which may have an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20242029      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   unexpected significance to themselves or others.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2025       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2030      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20262031      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   In particular, the convention has been established that the GET and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20272032      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HEAD methods SHOULD NOT have the significance of taking an action</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20302035      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   and DELETE, in a special way, so that the user is made aware of the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20312036      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   fact that a possibly unsafe action is being requested.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2032       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2037      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20332038      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Naturally, it is not possible to ensure that the server does not</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20342039      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   generate side-effects as a result of performing a GET request; in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20362041      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   distinction here is that the user did not request the side-effects,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20372042      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   so therefore cannot be held accountable for them.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2038       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2043      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20392044      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.1.2.  Idempotent Methods</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2040       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2045      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20412046      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Methods can also have the property of "idempotence" in that (aside</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20422047      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   from error or expiration issues) the side-effects of N &gt; 0 identical</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20442049      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   PUT and DELETE share this property.  Also, the methods OPTIONS and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20452050      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   TRACE SHOULD NOT have side effects, and so are inherently idempotent.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2046       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2051      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20472052      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   However, it is possible that a sequence of several requests is non-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20482053      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   idempotent, even if all of the methods executed in that sequence are</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20522057      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   sequence is non-idempotent if its result depends on a value that is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20532058      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   later modified in the same sequence.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2054       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2059      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20552060      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A sequence that never has side effects is idempotent, by definition</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20562061      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   (provided that no concurrent operations are being executed on the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20572062      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   same set of resources).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2058       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2063      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20592064      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.2.  OPTIONS</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2060       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2065      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20612066      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The OPTIONS method represents a request for information about the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20622067      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   communication options available on the request/response chain</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20652070      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   or the capabilities of a server, without implying a resource action</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20662071      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   or initiating a resource retrieval.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2067       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2072      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20682073      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Responses to this method are not cacheable.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2069       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2074      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20702075      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the OPTIONS request includes an entity-body (as indicated by the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20712076      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   presence of Content-Length or Transfer-Encoding), then the media type</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20752080      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   queries on the server.  A server that does not support such an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20762081      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   extension MAY discard the request body.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2077       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2082      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20782083      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the Request-URI is an asterisk ("*"), the OPTIONS request is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20792084      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   intended to apply to the server in general rather than to a specific</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20832088      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the capabilities of the server.  For example, this can be used to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20842089      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   test a proxy for HTTP/1.1 compliance (or lack thereof).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2085       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2090      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20862091      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the Request-URI is not an asterisk, the OPTIONS request applies</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20872092      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   only to the options that are available when communicating with that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20882093      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   resource.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2089       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2094      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20902095      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A 200 response SHOULD include any header fields that indicate</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20912096      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   optional features implemented by the server and applicable to that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    20982103      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the response MUST include a Content-Length field with a field-value</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20992104      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   of "0".</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2100       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2105      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21012106      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The Max-Forwards request-header field MAY be used to target a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21022107      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   specific proxy in the request chain.  When a proxy receives an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21102115      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request, then the forwarded request MUST NOT include a Max-Forwards</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21112116      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   field.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2112       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2117      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21132118      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.3.  GET</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2114       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2119      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21152120      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The GET method means retrieve whatever information (in the form of an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21162121      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity) is identified by the Request-URI.  If the Request-URI refers</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21182123      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   returned as the entity in the response and not the source text of the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21192124      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   process, unless that text happens to be the output of the process.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2120       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2125      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21212126      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The semantics of the GET method change to a "conditional GET" if the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21222127      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request message includes an If-Modified-Since, If-Unmodified-Since,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21272132      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   usage by allowing cached entities to be refreshed without requiring</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21282133      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   multiple requests or transferring data already held by the client.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2129       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2134      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21302135      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The semantics of the GET method change to a "partial GET" if the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21312136      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request message includes a Range header field.  A partial GET</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21342139      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   unnecessary network usage by allowing partially-retrieved entities to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21352140      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   be completed without transferring data already held by the client.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2136       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2141      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21372142      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The response to a GET request is cacheable if and only if it meets</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21382143      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the requirements for HTTP caching described in Section 13.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2139       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2144      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21402145      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   See Section 15.1.3 for security considerations when used for forms.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2141       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2146      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21422147      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.4.  HEAD</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2143       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2148      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21442149      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The HEAD method is identical to GET except that the server MUST NOT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21452150      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   return a message-body in the response.  The metainformation contained</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21502155      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   is often used for testing hypertext links for validity,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21512156      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   accessibility, and recent modification.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2152       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2157      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21532158      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The response to a HEAD request MAY be cacheable in the sense that the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21542159      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   information contained in the response MAY be used to update a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21582163      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   or Last-Modified), then the cache MUST treat the cache entry as</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21592164      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   stale.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2160       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2165      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21612166      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.5.  POST</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2162       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2167      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21632168      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The POST method is used to request that the origin server accept the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21642169      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity enclosed in the request as a new subordinate of the resource</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21652170      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   identified by the Request-URI in the Request-Line.  POST is designed</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21662171      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to allow a uniform method to cover the following functions:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2167       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2172      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21682173      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Annotation of existing resources;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2169       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2174      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21702175      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Posting a message to a bulletin board, newsgroup, mailing list, or</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21712176      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      similar group of articles;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2172       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2177      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21732178      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Providing a block of data, such as the result of submitting a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21742179      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      form, to a data-handling process;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2175       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2180      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21762181      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Extending a database through an append operation.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2177       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2182      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21782183      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The actual function performed by the POST method is determined by the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21792184      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   server and is usually dependent on the Request-URI.  The posted</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21822187      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   subordinate to a newsgroup to which it is posted, or a record is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21832188      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   subordinate to a database.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2184       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2189      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21852190      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The action performed by the POST method might not result in a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21862191      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   resource that can be identified by a URI.  In this case, either 200</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    21882193      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   depending on whether or not the response includes an entity that</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21892194      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   describes the result.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2190       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2195      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21912196      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If a resource has been created on the origin server, the response</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21922197      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   SHOULD be 201 (Created) and contain an entity which describes the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21932198      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   status of the request and refers to the new resource, and a Location</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21942199      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   header (see Section 14.30).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2195       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2200      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21962201      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Responses to this method are not cacheable, unless the response</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21972202      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   includes appropriate Cache-Control or Expires header fields.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21982203      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   However, the 303 (See Other) response can be used to direct the user</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21992204      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   agent to retrieve a cacheable resource.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2200       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2205      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22012206      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   POST requests MUST obey the message transmission requirements set out</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22022207      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   in Section 8.2.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2203       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2208      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22042209      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   See Section 15.1.3 for security considerations.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2205       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2210      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22062211      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.6.  PUT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2207       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2212      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22082213      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The PUT method requests that the enclosed entity be stored under the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22092214      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   supplied Request-URI.  If the Request-URI refers to an already</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    22232228      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   implement and MUST return a 501 (Not Implemented) response in such</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22242229      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   cases.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2225       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2230      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22262231      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the request passes through a cache and the Request-URI identifies</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22272232      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   one or more currently cached entities, those entries SHOULD be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22282233      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   treated as stale.  Responses to this method are not cacheable.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2229       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2234      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22302235      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The fundamental difference between the POST and PUT requests is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22312236      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   reflected in the different meaning of the Request-URI.  The URI in a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    22402245      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   user agent MAY then make its own decision regarding whether or not to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22412246      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   redirect the request.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2242       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2247      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22432248      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A single resource MAY be identified by many different URIs.  For</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22442249      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   example, an article might have a URI for identifying "the current</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    22462251      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   version.  In this case, a PUT request on a general URI might result</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22472252      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   in several other URIs being defined by the origin server.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2248       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2253      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22492254      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP/1.1 does not define how a PUT method affects the state of an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22502255      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   origin server.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2251       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2256      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22522257      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   PUT requests MUST obey the message transmission requirements set out</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22532258      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   in Section 8.2.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2254       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2259      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22552260      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Unless otherwise specified for a particular entity-header, the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22562261      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity-headers in the PUT request SHOULD be applied to the resource</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22572262      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   created or modified by the PUT.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2258       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2263      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22592264      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.7.  DELETE</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2260       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2265      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22612266      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The DELETE method requests that the origin server delete the resource</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22622267      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   identified by the Request-URI.  This method MAY be overridden by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    22682273      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   intends to delete the resource or move it to an inaccessible</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22692274      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   location.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2270       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2275      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22712276      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A successful response SHOULD be 200 (OK) if the response includes an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22722277      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity describing the status, 202 (Accepted) if the action has not</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22732278      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   yet been enacted, or 204 (No Content) if the action has been enacted</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22742279      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   but the response does not include an entity.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2275       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2280      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22762281      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the request passes through a cache and the Request-URI identifies</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22772282      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   one or more currently cached entities, those entries SHOULD be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22782283      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   treated as stale.  Responses to this method are not cacheable.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2279       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2284      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22802285      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.8.  TRACE</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2281       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2286      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22822287      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The TRACE method is used to invoke a remote, application-layer loop-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22832288      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   back of the request message.  The final recipient of the request</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    22872292      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   value of zero (0) in the request (see Section 14.31).  A TRACE</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22882293      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request MUST NOT include an entity.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2289       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2294      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22902295      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   TRACE allows the client to see what is being received at the other</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22912296      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   end of the request chain and use that data for testing or diagnostic</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    22952300      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   length of the request chain, which is useful for testing a chain of</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22962301      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   proxies forwarding messages in an infinite loop.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2297       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2302      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22982303      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the request is valid, the response SHOULD contain the entire</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    22992304      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request message in the entity-body, with a Content-Type of "message/</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23002305      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   http".  Responses to this method MUST NOT be cached.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2301       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2306      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23022307      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">9.9.  CONNECT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2303       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2308      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23042309      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This specification reserves the method name CONNECT for use with a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23052310      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   proxy that can dynamically switch to being a tunnel (e.g.  SSL</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23062311      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   tunneling [Luo1998]).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2307       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2312      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23082313      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.  Status Code Definitions</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2309       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2314      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23102315      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Each Status-Code is described below, including a description of which</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23112316      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   method(s) it can follow and any metainformation required in the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23122317      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2313       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2318      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23142319      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.1.  Informational 1xx</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2315       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2320      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23162321      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This class of status code indicates a provisional response,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23172322      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   consisting only of the Status-Line and optional headers, and is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    23202325      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23212326      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   except under experimental conditions.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2322       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2327      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23232328      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A client MUST be prepared to accept one or more 1xx status responses</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23242329      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   prior to a regular response, even if the client does not expect a 100</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23252330      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   (Continue) status message.  Unexpected 1xx status responses MAY be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23262331      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   ignored by a user agent.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2327       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2332      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23282333      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Proxies MUST forward 1xx responses, unless the connection between the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23292334      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   proxy and its client has been closed, or unless the proxy itself</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    23322337      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   then it need not forward the corresponding 100 (Continue)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23332338      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response(s).)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2334       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2339      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23352340      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.1.1.  100 Continue</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2336       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2341      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23372342      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The client SHOULD continue with its request.  This interim response</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23382343      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   is used to inform the client that the initial part of the request has</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    23432348      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   completed.  See Section 8.2.3 for detailed discussion of the use and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23442349      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   handling of this status code.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2345       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2350      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23462351      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.1.2.  101 Switching Protocols</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2347       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2352      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23482353      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The server understands and is willing to comply with the client's</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23492354      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request, via the Upgrade message header field (Section 14.42), for a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    23522357      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Upgrade header field immediately after the empty line which</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23532358      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   terminates the 101 response.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2354       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2359      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23552360      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The protocol SHOULD be switched only when it is advantageous to do</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23562361      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   so.  For example, switching to a newer version of HTTP is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    23582363      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   synchronous protocol might be advantageous when delivering resources</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23592364      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   that use such features.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2360       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2365      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23612366      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.  Successful 2xx</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2362       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2367      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23632368      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This class of status code indicates that the client's request was</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23642369      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   successfully received, understood, and accepted.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2365       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2370      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23662371      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.1.  200 OK</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2367       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2372      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23682373      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The request has succeeded.  The information returned with the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23692374      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response is dependent on the method used in the request, for example:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2370       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2375      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23712376      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   GET  an entity corresponding to the requested resource is sent in the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23722377      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      response;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2373       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2378      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23742379      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HEAD  the entity-header fields corresponding to the requested</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23752380      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      resource are sent in the response without any message-body;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23762381      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   POST  an entity describing or containing the result of the action;</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2377       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2382      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23782383      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   TRACE  an entity containing the request message as received by the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23792384      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      end server.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2380       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2385      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23812386      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.2.  201 Created</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2382       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2387      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23832388      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The request has been fulfilled and resulted in a new resource being</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23842389      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   created.  The newly created resource can be referenced by the URI(s)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    23922397      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the action cannot be carried out immediately, the server SHOULD</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23932398      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   respond with 202 (Accepted) response instead.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2394       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2399      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23952400      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A 201 response MAY contain an ETag response header field indicating</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23962401      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the current value of the entity tag for the requested variant just</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23972402      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   created, see Section 14.19.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2398       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2403      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    23992404      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.3.  202 Accepted</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2400       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2405      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24012406      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The request has been accepted for processing, but the processing has</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24022407      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   not been completed.  The request might or might not eventually be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24042409      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   place.  There is no facility for re-sending a status code from an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24052410      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   asynchronous operation such as this.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2406       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2411      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24072412      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The 202 response is intentionally non-committal.  Its purpose is to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24082413      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   allow a server to accept a request for some other process (perhaps a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24132418      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   and either a pointer to a status monitor or some estimate of when the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24142419      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   user can expect the request to be fulfilled.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2415       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2420      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24162421      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.4.  203 Non-Authoritative Information</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2417       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2422      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24182423      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The returned metainformation in the entity-header is not the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24192424      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   definitive set as available from the origin server, but is gathered</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24242429      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   this response code is not required and is only appropriate when the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24252430      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response would otherwise be 200 (OK).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2426       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2431      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24272432      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.5.  204 No Content</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2428       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2433      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24292434      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The server has fulfilled the request but does not need to return an</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24302435      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity-body, and might want to return updated metainformation.  The</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24322437      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   entity-headers, which if present SHOULD be associated with the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24332438      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   requested variant.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2434       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2439      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24352440      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the client is a user agent, it SHOULD NOT change its document view</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24362441      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   from that which caused the request to be sent.  This response is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24392444      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   any new or updated metainformation SHOULD be applied to the document</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24402445      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   currently in the user agent's active view.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2441       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2446      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24422447      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The 204 response MUST NOT include a message-body, and thus is always</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24432448      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   terminated by the first empty line after the header fields.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2444       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2449      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24452450      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.6.  205 Reset Content</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2446       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2451      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24472452      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The server has fulfilled the request and the user agent SHOULD reset</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24482453      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the document view which caused the request to be sent.  This response</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24512456      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   given so that the user can easily initiate another input action.  The</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24522457      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response MUST NOT include an entity.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2453       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2458      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24542459      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.2.7.  206 Partial Content</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2455       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2460      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24562461      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The server has fulfilled the partial GET request for the resource.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24572462      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The request MUST have included a Range header field (Section 14.35)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24582463      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   indicating the desired range, and MAY have included an If-Range</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24592464      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   header field (Section 14.27) to make the request conditional.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2460       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2465      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24612466      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The response MUST include the following header fields:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2462       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2467      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24632468      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Either a Content-Range header field (Section 14.16) indicating the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24642469      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      range included with this response, or a multipart/byteranges</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24672472      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      MUST match the actual number of OCTETs transmitted in the message-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24682473      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      body.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2469       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2474      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24702475      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Date</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24712476      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  ETag and/or Content-Location, if the header would have been sent</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24722477      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      in a 200 response to the same request</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2473       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2478      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24742479      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Expires, Cache-Control, and/or Vary, if the field-value might</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24752480      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      differ from that sent in any previous response for the same</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24762481      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      variant</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2477       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2482      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24782483      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the 206 response is the result of an If-Range request that used a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24792484      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   strong cache validator (see Section 13.3.3), the response SHOULD NOT</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    24842489      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   MUST include all of the entity-headers that would have been returned</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24852490      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   with a 200 (OK) response to the same request.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2486       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2491      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24872492      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A cache MUST NOT combine a 206 response with other previously cached</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24882493      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   content if the ETag or Last-Modified headers do not match exactly,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24892494      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   see 13.5.4.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2490       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2495      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24912496      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A cache that does not support the Range and Content-Range headers</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24922497      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   MUST NOT cache 206 (Partial) responses.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2493       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2498      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24942499      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.3.  Redirection 3xx</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2495       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2500      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24962501      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This class of status code indicates that further action needs to be</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    24972502      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   taken by the user agent in order to fulfill the request.  The action</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    25002505      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   GET or HEAD.  A client SHOULD detect infinite redirection loops,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25012506      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   since such loops generate network traffic for each redirection.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2502       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2507      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25032508      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: previous versions of this specification recommended a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25042509      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      maximum of five redirections.  Content developers should be aware</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25052510      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      that there might be clients that implement such a fixed</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25062511      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      limitation.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2507       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2512      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25082513      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.3.1.  300 Multiple Choices</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2509       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2514      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25102515      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The requested resource corresponds to any one of a set of</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25112516      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   representations, each with its own specific location, and agent-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    25132518      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the user (or user agent) can select a preferred representation and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25142519      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   redirect its request to that location.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2515       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2520      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25162521      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Unless it was a HEAD request, the response SHOULD include an entity</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25172522      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   containing a list of resource characteristics and location(s) from</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25182523      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   which the user or user agent can choose the one most appropriate.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2519       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2524      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25202525      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The entity format is specified by the media type given in the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25212526      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Content-Type header field.  Depending upon the format and the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    25232528      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   choice MAY be performed automatically.  However, this specification</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25242529      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   does not define any standard for such automatic selection.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2525       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2530      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25262531      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the server has a preferred choice of representation, it SHOULD</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25272532      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   include the specific URI for that representation in the Location</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25282533      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   field; user agents MAY use the Location field value for automatic</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25292534      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   redirection.  This response is cacheable unless indicated otherwise.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2530       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2535      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25312536      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.3.2.  301 Moved Permanently</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2532       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2537      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25332538      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The requested resource has been assigned a new permanent URI and any</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25342539      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   future references to this resource SHOULD use one of the returned</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    25372542      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   references returned by the server, where possible.  This response is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25382543      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   cacheable unless indicated otherwise.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2539       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2544      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25402545      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The new permanent URI SHOULD be given by the Location field in the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25412546      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response.  Unless the request method was HEAD, the entity of the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25422547      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response SHOULD contain a short hypertext note with a hyperlink to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25432548      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the new URI(s).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2544       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2549      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25452550      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the 301 status code is received in response to a request other</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25462551      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   than GET or HEAD, the user agent MUST NOT automatically redirect the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25472552      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request unless it can be confirmed by the user, since this might</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25482553      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   change the conditions under which the request was issued.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2549       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2554      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25502555      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: When automatically redirecting a POST request after</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25512556      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      receiving a 301 status code, some existing HTTP/1.0 user agents</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25522557      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      will erroneously change it into a GET request.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2553       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2558      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25542559      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.3.3.  302 Found</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2555       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2560      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25562561      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The requested resource resides temporarily under a different URI.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25572562      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Since the redirection might be altered on occasion, the client SHOULD</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    25592564      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   is only cacheable if indicated by a Cache-Control or Expires header</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25602565      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   field.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2561       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2566      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25622567      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The temporary URI SHOULD be given by the Location field in the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25632568      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response.  Unless the request method was HEAD, the entity of the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25642569      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response SHOULD contain a short hypertext note with a hyperlink to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25652570      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the new URI(s).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2566       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2571      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25672572      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the 302 status code is received in response to a request other</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25682573      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   than GET or HEAD, the user agent MUST NOT automatically redirect the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25692574      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   request unless it can be confirmed by the user, since this might</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25702575      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   change the conditions under which the request was issued.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2571       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2576      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25722577      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: RFC 1945 and RFC 2068 specify that the client is not allowed</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25732578      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      to change the method on the redirected request.  However, most</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    25772582      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      been added for servers that wish to make unambiguously clear which</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25782583      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      kind of reaction is expected of the client.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2579       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2584      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25802585      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.3.4.  303 See Other</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2581       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2586      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25822587      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The response to the request can be found under a different URI and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25832588      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   SHOULD be retrieved using a GET method on that resource.  This method</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    25872592      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response MUST NOT be cached, but the response to the second</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25882593      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   (redirected) request might be cacheable.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2589       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2594      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25902595      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The different URI SHOULD be given by the Location field in the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25912596      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response.  Unless the request method was HEAD, the entity of the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25922597      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   response SHOULD contain a short hypertext note with a hyperlink to</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25932598      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the new URI(s).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2594       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2599      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25952600      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: Many pre-HTTP/1.1 user agents do not understand the 303</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25962601      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      status.  When interoperability with such clients is a concern, the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25972602      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      302 status code may be used instead, since most user agents react</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    25982603      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      to a 302 response as described here for 303.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2599       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2604      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26002605      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.3.5.  304 Not Modified</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2601       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2606      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26022607      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the client has performed a conditional GET request and access is</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26032608      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   allowed, but the document has not been modified, the server SHOULD</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    26052610      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   message-body, and thus is always terminated by the first empty line</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26062611      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   after the header fields.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2607       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2612      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26082613      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The response MUST include the following header fields:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2609       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2614      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26102615      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Date, unless its omission is required by Section 14.18.1</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2611       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2616      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26122617      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If a clockless origin server obeys these rules, and proxies and</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26132618      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   clients add their own Date to any response received without one (as</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26142619      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   already specified by [RFC 2068], section 14.19), caches will operate</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26152620      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   correctly.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2616       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2621      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26172622      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  ETag and/or Content-Location, if the header would have been sent</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26182623      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      in a 200 response to the same request</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2619       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2624      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26202625      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Expires, Cache-Control, and/or Vary, if the field-value might</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26212626      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      differ from that sent in any previous response for the same</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26222627      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      variant</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2623       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2628      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26242629      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If the conditional GET used a strong cache validator (see</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26252630      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Section 13.3.3), the response SHOULD NOT include other entity-</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    26282633      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   prevents inconsistencies between cached entity-bodies and updated</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26292634      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   headers.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2630       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2635      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26312636      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If a 304 response indicates an entity not currently cached, then the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26322637      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   cache MUST disregard the response and repeat the request without the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26332638      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   conditional.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2634       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2639      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26352640      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   If a cache uses a received 304 response to update a cache entry, the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26362641      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   cache MUST update the entry to reflect any new field values given in</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26372642      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the response.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2638       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2643      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26392644      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">10.3.6.  305 Use Proxy</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2640       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2645      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26412646      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The requested resource MUST be accessed through the proxy given by</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26422647      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the Location field.  The Location field gives the URI of the proxy.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26432648      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   The recipient is expected to repeat this single request via the</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26442649      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   proxy. 305 responses MUST only be generated by origin servers.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2645       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2650      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26462651      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      Note: RFC 2068 was not clear that 305 was intended to redirect a</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    26472652      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      single request, and to be generated by origin servers only.  Not</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2648265