Ignore:
Timestamp:
06/05/14 16:45:07 (6 years ago)
Author:
julian.reschke@…
Message:

avoid line breaks in charset names (#553)

Location:
draft-ietf-httpbis/latest
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt

    r2648 r2649  
    14381438   value.
    14391439
    1440    Historically, HTTP has allowed field content with text in the ISO-
    1441    8859-1 [ISO-8859-1] charset, supporting other charsets only through
    1442    use of [RFC2047] encoding.  In practice, most HTTP header field
    1443    values use only a subset of the US-ASCII charset [USASCII].  Newly
    1444    defined header fields SHOULD limit their field values to US-ASCII
    1445    octets.  A recipient SHOULD treat other octets in field content (obs-
    1446    text) as opaque data.
     1440   Historically, HTTP has allowed field content with text in the
     1441   ISO-8859-1 charset [ISO-8859-1], supporting other charsets only
     1442   through use of [RFC2047] encoding.  In practice, most HTTP header
     1443   field values use only a subset of the US-ASCII charset [USASCII].
     1444   Newly defined header fields SHOULD limit their field values to
     1445   US-ASCII octets.  A recipient SHOULD treat other octets in field
     1446   content (obs-text) as opaque data.
    14471447
    144814483.2.5.  Field Limits
  • draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt

    r2648 r2649  
    687687OLD:
    688688
    689     Historically, HTTP has allowed field content with text in the ISO-
    690     8859-1 [ISO-8859-1] charset, supporting other charsets only through
    691     use of [RFC2047] encoding.  In practice, most HTTP header field
    692     values use only a subset of the US-ASCII charset [USASCII].  Newly
    693     defined header fields SHOULD limit their field values to US-ASCII
    694     octets.  A recipient SHOULD treat other octets in field content (obs-
    695     text) as opaque data.
     689    Historically, HTTP has allowed field content with text in the
     690    ISO-8859-1 charset [ISO-8859-1], supporting other charsets only
     691    through use of [RFC2047] encoding.  In practice, most HTTP header
     692    field values use only a subset of the US-ASCII charset [USASCII].
     693    Newly defined header fields SHOULD limit their field values to
     694    US-ASCII octets.  A recipient SHOULD treat other octets in field
     695    content (obs-text) as opaque data.
    696696
    697697NEW:
  • draft-ietf-httpbis/latest/auth48/rfc7230.diff.html

    r2648 r2649  
    582582      <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>
    583583      <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>
    586585      <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>
    587586      <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>
     
    593592      <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>
    594593      <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>
    595595      <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>
    603602      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    604603      <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>
     
    606605      <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>
    607606      <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>
    613607      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    614608      <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>
     
    16721666     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    16731667     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 110 change blocks.&nbsp;</a></th></tr>
    1674      <tr class="stats"><td></td><th><i>193 lines changed or deleted</i></th><th><i> </i></th><th><i>172 lines 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>
    16751669     <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>
    16761670   </table>
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2648 r2649  
    13961396               <p id="rfc.section.3.2.4.p.7">A user agent that receives an <a href="#header.fields" class="smpl">obs-fold</a> in a response message that is not within a message/http container <em class="bcp14">MUST</em> replace each received <a href="#header.fields" class="smpl">obs-fold</a> with one or more <a href="#core.rules" class="smpl">SP</a> octets prior to interpreting the field value.
    13971397               </p>
    1398                <p id="rfc.section.3.2.4.p.8">Historically, HTTP has allowed field content with text in the ISO-8859-1 <a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a> charset, supporting other charsets only through use of <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a> encoding. In practice, most HTTP header field values use only a subset of the US-ASCII charset <a href="#USASCII" id="rfc.xref.USASCII.3"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a>. Newly defined header fields <em class="bcp14">SHOULD</em> limit their field values to US-ASCII octets. A recipient <em class="bcp14">SHOULD</em> treat other octets in field content (obs-text) as opaque data.
     1398               <p id="rfc.section.3.2.4.p.8">Historically, HTTP has allowed field content with text in the ISO‑8859‑1 charset <a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>, supporting other charsets only through use of <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a> encoding. In practice, most HTTP header field values use only a subset of the US-ASCII charset <a href="#USASCII" id="rfc.xref.USASCII.3"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a>. Newly defined header fields <em class="bcp14">SHOULD</em> limit their field values to US‑ASCII octets. A recipient <em class="bcp14">SHOULD</em> treat other octets in field content (obs‑text) as opaque data.
    13991399               </p>
    14001400            </div>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2648 r2649  
    1616  <!ENTITY ID-YEAR "2014">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY nbhy  "&#x2011;">
    1819  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1920  <!ENTITY caching-overview       "<xref target='RFC7234' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    14171418</t>
    14181419<t>
    1419    Historically, HTTP has allowed field content with text in the ISO-8859-1
    1420    <xref target="ISO-8859-1"/> charset, supporting other charsets only
     1420   Historically, HTTP has allowed field content with text in the ISO&nbhy;8859&nbhy;1
     1421   charset <xref target="ISO-8859-1"/>, supporting other charsets only
    14211422   through use of <xref target="RFC2047"/> encoding.
    14221423   In practice, most HTTP header field values use only a subset of the
    14231424   US-ASCII charset <xref target="USASCII"/>. Newly defined
    1424    header fields &SHOULD; limit their field values to US-ASCII octets.
    1425    A recipient &SHOULD; treat other octets in field content (obs-text) as
     1425   header fields &SHOULD; limit their field values to US&nbhy;ASCII octets.
     1426   A recipient &SHOULD; treat other octets in field content (obs&nbhy;text) as
    14261427   opaque data.
    14271428</t>
Note: See TracChangeset for help on using the changeset viewer.