01/09/11 01:23:29 (11 years ago)

Fix incorrect definition of line folding (obs-fold) from [351].
Remove optional WSP from chunked encoding grammar added in [353].
Do not use WSP anywhere (it is misleading because it dosn't match the real
definition of whitespace).

Related to #36

1 edited


  • draft-ietf-httpbis/latest/p2-semantics.html

    r1421 r1425  
    736736      </p>
    737737      <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    738          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    739          and WSP (whitespace).
     738         (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
     739         (any visible US-ASCII character).
    740740      </p>
    741741      <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    10361036      </p>
    10371037      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    = 3<a href="#notation" class="smpl">DIGIT</a>
    1038   <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#notation" class="smpl">WSP</a> / <a href="#notation" class="smpl">VCHAR</a> / <a href="#core.rules" class="smpl">obs-text</a> )
     1038  <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#notation" class="smpl">HTAB</a> / <a href="#notation" class="smpl">SP</a> / <a href="#notation" class="smpl">VCHAR</a> / <a href="#core.rules" class="smpl">obs-text</a> )
    10391039</pre><p id="rfc.section.4.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    10401040         though such understanding is obviously desirable. However, applications <em class="bcp14">MUST</em> understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent
    28112811<a href="#core.rules" class="smpl">RWS</a> = &lt;RWS, defined in [Part1], Section 1.2.2&gt;
    2812 <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *( WSP / VCHAR / obs-text )
     2812<a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *( HTAB / SP / VCHAR / obs-text )
    28132813<a href="#header.referer" class="smpl">Referer</a> = absolute-URI / partial-URI
    28142814<a href="#header.retry-after" class="smpl">Retry-After</a> = HTTP-date / delta-seconds
Note: See TracChangeset for help on using the changeset viewer.