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/p7-auth.xml

    r1681 r1682  
    167167</t>
    168168<t>
    169    Unless noted otherwise, Recipients &MAY; take steps to recover a usable
    170    protocol element from an invalid construct. However, HTTP does not define
     169   Unless noted otherwise, Recipients &MUST; be able to parse all protocol
     170   elements matching the ABNF rules defined for them and &MAY; take steps to
     171   recover a usable protocol element from an invalid construct. However, HTTP does not define
    171172   specific error handling mechanisms, except in cases where it has direct
    172173   impact on security. This is because different uses of the protocol require
     
    11641165      "Authentication exchanges"
    11651166    </t>
     1167    <t>
     1168      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
     1169      "ABNF requirements for recipients"
     1170    </t>
    11661171  </list>
    11671172</t>
Note: See TracChangeset for help on using the changeset viewer.