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/p4-conditional.xml

    r1667 r1682  
    192192</t>
    193193<t>
    194    Unless noted otherwise, Recipients &MAY; take steps to recover a usable
    195    protocol element from an invalid construct. However, HTTP does not define
     194   Unless noted otherwise, Recipients &MUST; be able to parse all protocol
     195   elements matching the ABNF rules defined for them and &MAY; take steps to
     196   recover a usable protocol element from an invalid construct. However, HTTP does not define
    196197   specific error handling mechanisms, except in cases where it has direct
    197198   impact on security. This is because different uses of the protocol require
     
    14091410<section title="Since draft-ietf-httpbis-p4-conditional-19" anchor="changes.since.19">
    14101411<t>
    1411   None yet.
     1412  Closed issues:
     1413  <list style="symbols">
     1414    <t>
     1415      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
     1416      "ABNF requirements for recipients"
     1417    </t>
     1418  </list>
    14121419</t>
    14131420</section>
Note: See TracChangeset for help on using the changeset viewer.