Changeset 2649 for draft-ietf-httpbis/latest/auth48/rfc7230.diff.html
- Timestamp:
- 06/05/14 16:45:07 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/auth48/rfc7230.diff.html
r2648 r2649 582 582 <tr><td class="lineno" valign="top"></td><td class="left"> server MUST reject any received request message that contains</td><td> </td><td class="right"> server MUST reject any received request message that contains</td><td class="lineno" valign="top"></td></tr> 583 583 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 584 <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 26, line 15</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 26, line 15</em></th><td></td></tr> 585 <tr><td class="lineno" valign="top"></td><td class="left"> with a representation explaining that unacceptable line folding was</td><td> </td><td class="right"> with a representation explaining that unacceptable line folding was</td><td class="lineno" valign="top"></td></tr> 584 <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 26, line 16</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 26, line 16</em></th><td></td></tr> 586 585 <tr><td class="lineno" valign="top"></td><td class="left"> received, or replace each received obs-fold with one or more SP</td><td> </td><td class="right"> received, or replace each received obs-fold with one or more SP</td><td class="lineno" valign="top"></td></tr> 587 586 <tr><td class="lineno" valign="top"></td><td class="left"> octets prior to interpreting the field value or forwarding the</td><td> </td><td class="right"> octets prior to interpreting the field value or forwarding the</td><td class="lineno" valign="top"></td></tr> … … 593 592 <tr><td class="lineno" valign="top"></td><td class="left"> value.</td><td> </td><td class="right"> value.</td><td class="lineno" valign="top"></td></tr> 594 593 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 594 <tr><td class="lineno" valign="top"></td><td class="left"> Historically, HTTP has allowed field content with text in the</td><td> </td><td class="right"> Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr> 595 595 <tr><td><a name="diff0031" /></td></tr> 596 <tr><td class="lineno" valign="top"></td><td class="lblock"> Historically, HTTP has allowed field content with text in the <span class="delete">ISO-</span></td><td> </td><td class="rblock"> Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr> 597 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> 8859-1</span> [ISO-8859-1] charset, supporting other charsets only through</td><td> </td><td class="rblock"> <span class="insert">ISO-8859-1</span> [ISO-8859-1] charset, supporting other charsets only</td><td class="lineno" valign="top"></td></tr> 598 <tr><td class="lineno" valign="top"></td><td class="lblock"> use of [RFC2047] encoding. In practice, most HTTP header field</td><td> </td><td class="rblock"> through use of [RFC2047] encoding. In practice, most HTTP header</td><td class="lineno" valign="top"></td></tr> 599 <tr><td class="lineno" valign="top"></td><td class="lblock"> values use only a subset of the US-ASCII charset [USASCII]. Newly</td><td> </td><td class="rblock"> field values use only a subset of the US-ASCII charset [USASCII].</td><td class="lineno" valign="top"></td></tr> 600 <tr><td class="lineno" valign="top"></td><td class="lblock"> defined header fields SHOULD limit their field values to US-ASCII</td><td> </td><td class="rblock"> Newly defined header fields SHOULD limit their field values to</td><td class="lineno" valign="top"></td></tr> 601 <tr><td class="lineno" valign="top"></td><td class="lblock"> octets. A recipient SHOULD treat other octets in field content <span class="delete">(obs-</span></td><td> </td><td class="rblock"> US-ASCII octets. A recipient SHOULD treat other octets in field</td><td class="lineno" valign="top"></td></tr> 602 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> text)</span> as opaque data.</td><td> </td><td class="rblock"> content <span class="insert">(obs-text)</span> as opaque data.</td><td class="lineno" valign="top"></td></tr> 596 <tr><td class="lineno" valign="top"></td><td class="lblock"> ISO-8859-1 <span class="delete">charset [ISO-8859-1]</span>, supporting other charsets only</td><td> </td><td class="rblock"> ISO-8859-1 <span class="insert">[ISO-8859-1] charset</span>, supporting other charsets only</td><td class="lineno" valign="top"></td></tr> 597 <tr><td class="lineno" valign="top"></td><td class="left"> through use of [RFC2047] encoding. In practice, most HTTP header</td><td> </td><td class="right"> through use of [RFC2047] encoding. In practice, most HTTP header</td><td class="lineno" valign="top"></td></tr> 598 <tr><td class="lineno" valign="top"></td><td class="left"> field values use only a subset of the US-ASCII charset [USASCII].</td><td> </td><td class="right"> field values use only a subset of the US-ASCII charset [USASCII].</td><td class="lineno" valign="top"></td></tr> 599 <tr><td class="lineno" valign="top"></td><td class="left"> Newly defined header fields SHOULD limit their field values to</td><td> </td><td class="right"> Newly defined header fields SHOULD limit their field values to</td><td class="lineno" valign="top"></td></tr> 600 <tr><td class="lineno" valign="top"></td><td class="left"> US-ASCII octets. A recipient SHOULD treat other octets in field</td><td> </td><td class="right"> US-ASCII octets. A recipient SHOULD treat other octets in field</td><td class="lineno" valign="top"></td></tr> 601 <tr><td class="lineno" valign="top"></td><td class="left"> content (obs-text) as opaque data.</td><td> </td><td class="right"> content (obs-text) as opaque data.</td><td class="lineno" valign="top"></td></tr> 603 602 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 604 603 <tr><td class="lineno" valign="top"></td><td class="left">3.2.5. Field Limits</td><td> </td><td class="right">3.2.5. Field Limits</td><td class="lineno" valign="top"></td></tr> … … 606 605 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP does not place a predefined limit on the length of each header</td><td> </td><td class="right"> HTTP does not place a predefined limit on the length of each header</td><td class="lineno" valign="top"></td></tr> 607 606 <tr><td class="lineno" valign="top"></td><td class="left"> field or on the length of the header section as a whole, as described</td><td> </td><td class="right"> field or on the length of the header section as a whole, as described</td><td class="lineno" valign="top"></td></tr> 608 <tr><td class="lineno" valign="top"></td><td class="left"> in Section 2.5. Various ad hoc limitations on individual header</td><td> </td><td class="right"> in Section 2.5. Various ad hoc limitations on individual header</td><td class="lineno" valign="top"></td></tr>609 <tr><td class="lineno" valign="top"></td><td class="left"> field length are found in practice, often depending on the specific</td><td> </td><td class="right"> field length are found in practice, often depending on the specific</td><td class="lineno" valign="top"></td></tr>610 <tr><td class="lineno" valign="top"></td><td class="left"> field semantics.</td><td> </td><td class="right"> field semantics.</td><td class="lineno" valign="top"></td></tr>611 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>612 <tr><td class="lineno" valign="top"></td><td class="left"> A server that receives a request header field, or set of fields,</td><td> </td><td class="right"> A server that receives a request header field, or set of fields,</td><td class="lineno" valign="top"></td></tr>613 607 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 614 608 <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 33, line 6</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 33, line 6</em></th><td></td></tr> … … 1672 1666 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 1673 1667 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 110 change blocks. </a></th></tr> 1674 <tr class="stats"><td></td><th><i>1 93 lines changed or deleted</i></th><th><i> </i></th><th><i>172lines changed or added</i></th><td></td></tr>1668 <tr class="stats"><td></td><th><i>187 lines changed or deleted</i></th><th><i> </i></th><th><i>166 lines changed or added</i></th><td></td></tr> 1675 1669 <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr> 1676 1670 </table>
Note: See TracChangeset
for help on using the changeset viewer.