Ignore:
Timestamp:
Oct 23, 2011, 1:20:31 PM (8 years ago)
Author:
julian.reschke@…
Message:

Rephrase description of conformance; explain how the spec handles error handling (see #186)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1443 r1452  
    1616  <!ENTITY ID-YEAR "2011">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1819  <!ENTITY notation                 "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1920  <!ENTITY notation-abnf            "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    267268</section>
    268269
    269 <section title="Requirements" anchor="intro.requirements">
     270<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
    270271<t>
    271272   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     
    274275</t>
    275276<t>
    276    An implementation is not compliant if it fails to satisfy one or more
    277    of the "MUST" or "REQUIRED" level requirements for the protocols it
    278    implements. An implementation that satisfies all the "MUST" or "REQUIRED"
    279    level and all the "SHOULD" level requirements for its protocols is said
    280    to be "unconditionally compliant"; one that satisfies all the "MUST"
    281    level requirements but not all the "SHOULD" level requirements for its
    282    protocols is said to be "conditionally compliant".
     277   This document defines conformance criteria for several roles in HTTP
     278   communication, including Senders, Recipients, Clients, Servers, User-Agents,
     279   Origin Servers, Intermediaries, Proxies and Gateways. See &architecture;
     280   for definitions of these terms.
     281</t>
     282<t>
     283   An implementation is considered conformant if it complies with all of the
     284   requirements associated with its role(s). Note that SHOULD-level requirements
     285   are relevant here, unless one of the documented exceptions is applicable.
     286</t>
     287<t>
     288   This document also uses ABNF to define valid protocol elements
     289   (<xref target="notation"/>). In addition to the prose requirements placed
     290   upon them, Senders &MUST-NOT; generate protocol elements that are invalid.
     291</t>
     292<t>
     293   Unless noted otherwise, Recipients &MAY; take steps to recover a usable
     294   protocol element from an invalid construct. However, HTTP does not define
     295   specific error handling mechanisms, except in cases where it has direct
     296   impact on security. This is because different uses of the protocol require
     297   different error handling strategies; for example, a Web browser may wish to
     298   transparently recover from a response where the Location header field
     299   doesn't parse according to the ABNF, whereby in a systems control protocol
     300   using HTTP, this type of error recovery could lead to dangerous consequences.
    283301</t>
    284302</section>
     
    30353053<section title="Since draft-ietf-httpbis-p3-payload-16" anchor="changes.since.16">
    30363054<t>
    3037   None yet.
     3055  Closed issues:
     3056  <list style="symbols">
     3057    <t>
     3058      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/186"/>:
     3059      "Document HTTP's error-handling philosophy"
     3060    </t>
     3061  </list>
    30383062</t>
    30393063</section>
Note: See TracChangeset for help on using the changeset viewer.