Ignore:
Timestamp:
Jun 21, 2012, 2:01:49 AM (7 years ago)
Author:
julian.reschke@…
Message:

Clarify that in general recipients MUST be able to parse everything allowed by the ABNF (see #361)

File:
1 edited

Legend:

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

    r1680 r1682  
    300300</t>
    301301<t>
    302    Unless noted otherwise, Recipients &MAY; take steps to recover a usable
    303    protocol element from an invalid construct. However, HTTP does not define
     302   Unless noted otherwise, Recipients &MUST; be able to parse all protocol
     303   elements matching the ABNF rules defined for them and &MAY; take steps to
     304   recover a usable protocol element from an invalid construct. However, HTTP does not define
    304305   specific error handling mechanisms, except in cases where it has direct
    305306   impact on security. This is because different uses of the protocol require
     
    67646765</section>
    67656766
    6766 <section title="Since draft-ietf-httpbis-p2-semantics-19" anchor="changes.since.19">
     6767<section title="Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19" anchor="changes.since.19">
    67676768<t>
    67686769  Closed issues:
     
    67726773      "should there be a permanent variant of 307"
    67736774    </t>
     6775    <t>
     6776      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
     6777      "ABNF requirements for recipients"
     6778    </t>
    67746779  </list>
    6775 </t>
    6776 </section>
    6777 
    6778 <section title="Since draft-ietf-httpbis-p3-payload-19" anchor="changes.3.since.19">
    6779 <t>
    6780   None yet.
    67816780</t>
    67826781</section>
Note: See TracChangeset for help on using the changeset viewer.