Changeset 154 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 05/01/08 14:13:28 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r153 r154 670 670 indentation of continuation lines is used to indicate a rule 671 671 definition that spans more than one line. Certain basic rules are 672 in uppercase, such as SP, LWS, HT , CRLF, DIGIT, ALPHA, etc. Angle672 in uppercase, such as SP, LWS, HTAB, CRLF, DIGIT, ALPHA, etc. Angle 673 673 brackets are used within definitions whenever their presence will 674 674 facilitate discerning the use of rule names. … … 806 806 <x:anchor-alias value="LF"/> 807 807 <x:anchor-alias value="SP"/> 808 <x:anchor-alias value="HT "/>808 <x:anchor-alias value="HTAB"/> 809 809 <x:anchor-alias value="CRLF"/> 810 810 <x:anchor-alias value="LWS"/> … … 823 823 is defined by ANSI X3.4-1986 <xref target="USASCII"/>. 824 824 </t> 825 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OCTET"/><iref primary="true" item="Grammar" subitem="CHAR"/><iref primary="true" item="Grammar" subitem="UPALPHA"/><iref primary="true" item="Grammar" subitem="LOALPHA"/><iref primary="true" item="Grammar" subitem="ALPHA"/><iref primary="true" item="Grammar" subitem="DIGIT"/><iref primary="true" item="Grammar" subitem="CTL"/><iref primary="true" item="Grammar" subitem="CR"/><iref primary="true" item="Grammar" subitem="LF"/><iref primary="true" item="Grammar" subitem="SP"/><iref primary="true" item="Grammar" subitem="HT "/>825 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OCTET"/><iref primary="true" item="Grammar" subitem="CHAR"/><iref primary="true" item="Grammar" subitem="UPALPHA"/><iref primary="true" item="Grammar" subitem="LOALPHA"/><iref primary="true" item="Grammar" subitem="ALPHA"/><iref primary="true" item="Grammar" subitem="DIGIT"/><iref primary="true" item="Grammar" subitem="CTL"/><iref primary="true" item="Grammar" subitem="CR"/><iref primary="true" item="Grammar" subitem="LF"/><iref primary="true" item="Grammar" subitem="SP"/><iref primary="true" item="Grammar" subitem="HTAB"/><iref primary="true" item="Grammar" subitem="DQUOTE"/> 826 826 OCTET = <any 8-bit sequence of data> 827 827 CHAR = <any US-ASCII character (octets 0 - 127)> … … 835 835 LF = <US-ASCII LF, linefeed (10)> 836 836 SP = <US-ASCII SP, space (32)> 837 HT 838 <">= <US-ASCII double-quote mark (34)>837 HTAB = <US-ASCII HT, horizontal-tab (9)> 838 DQUOTE = <US-ASCII double-quote mark (34)> 839 839 </artwork></figure> 840 840 <t> … … 855 855 </t> 856 856 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="LWS"/> 857 LWS = [CRLF] 1*( SP | HT )857 LWS = [CRLF] 1*( SP | HTAB ) 858 858 </artwork></figure> 859 859 <t> … … 889 889 token = 1*<any CHAR except CTLs or separators> 890 890 separators = "(" | ")" | "<" | ">" | "@" 891 | "," | ";" | ":" | "\" | <">891 | "," | ";" | ":" | "\" | DQUOTE 892 892 | "/" | "[" | "]" | "?" | "=" 893 | "{" | "}" | SP | HT 893 | "{" | "}" | SP | HTAB 894 894 </artwork></figure> 895 895 <t> … … 909 909 </t> 910 910 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-string"/><iref primary="true" item="Grammar" subitem="qdtext"/> 911 quoted-string = ( <"> *(qdtext | quoted-pair ) <">)912 qdtext = <any TEXT excluding <">and "\">911 quoted-string = ( DQUOTE *(qdtext | quoted-pair ) DQUOTE ) 912 qdtext = <any TEXT excluding DQUOTE and "\"> 913 913 </artwork></figure> 914 914 <t> … … 1357 1357 of LWS, though a single SP is preferred. Header fields can be 1358 1358 extended over multiple lines by preceding each extra line with at 1359 least one SP or HT . Applications ought to follow "common form", where1359 least one SP or HTAB. Applications ought to follow "common form", where 1360 1360 one is known or indicated, when generating HTTP constructs, since 1361 1361 there might exist some implementations that fail to accept anything … … 3806 3806 Clients &SHOULD; be tolerant in parsing the Status-Line and servers 3807 3807 tolerant when parsing the Request-Line. In particular, they &SHOULD; 3808 accept any amount of SP or HT characters between fields, even though3808 accept any amount of SP or HTAB characters between fields, even though 3809 3809 only a single SP is required. 3810 3810 </t> … … 4133 4133 Update media type registrations to use RFC4288 template. 4134 4134 </t> 4135 <t> 4136 Use names of RFC4234 core rules DQUOTE and HTAB (work in progress on <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>) 4137 </t> 4135 4138 </list> 4136 4139 </t>
Note: See TracChangeset
for help on using the changeset viewer.