Ignore:
Timestamp:
10/09/12 02:46:17 (8 years ago)
Author:
fielding@…
Message:

Be more consistent regarding targeting conformance requirements.
Only define conformance criteria once, but repeat required nits.

Remove antiquated requirement about media type parameters not being
recognized by 1993-era browsers.

Add reference to TLS in p1.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1868 r1875  
    15311531  <iref primary="true" item="Methods" subitem="TRACE" x:for-anchor=""/>
    15321532<t>
    1533    The TRACE method requests a remote, application-layer loop-back
     1533   The TRACE method requests a remote, application-level loop-back
    15341534   of the request message. The final recipient of the request
    15351535   &SHOULD; reflect the message received back to the client as the message body
     
    39603960</t>
    39613961<t>
    3962    Note that some older HTTP applications do not recognize media type
    3963    parameters. When sending data to older HTTP applications,
    3964    implementations &SHOULD; only use media type parameters when they are
    3965    required by that type/subtype definition.
    3966 </t>
    3967 <t>
    39683962   Media-type values are registered with the Internet Assigned Number
    39693963   Authority (IANA). The media type registration process is
     
    40064000   one or more representations within a single message body. All multipart
    40074001   types share a common syntax, as defined in <xref target="RFC2046" x:sec="5.1.1" x:fmt="of"/>,
    4008    and &MUST; include a boundary parameter as part of the media type
    4009    value. The message body is itself a protocol element and &MUST;
    4010    therefore use only CRLF to represent line breaks between body-parts.
     4002   and include a boundary parameter as part of the media type
     4003   value. The message body is itself a protocol element; a sender &MUST;
     4004   generate only CRLF to represent line breaks between body-parts.
    40114005</t>
    40124006<t>
     
    40224016</t>
    40234017<t>
    4024    If an application receives an unrecognized multipart subtype, the
    4025    application &MUST; treat it as being equivalent to "multipart/mixed".
     4018   A recipient &MUST; treat an unrecognized multipart subtype
     4019   as being equivalent to "multipart/mixed".
    40264020</t>
    40274021<x:note>
Note: See TracChangeset for help on using the changeset viewer.