Ignore:
Timestamp:
21/06/12 09:01:49 (8 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/p6-cache.xml

    r1675 r1682  
    326326</t>
    327327<t>
    328    Unless noted otherwise, Recipients &MAY; take steps to recover a usable
    329    protocol element from an invalid construct. However, HTTP does not define
     328   Unless noted otherwise, Recipients &MUST; be able to parse all protocol
     329   elements matching the ABNF rules defined for them and &MAY; take steps to
     330   recover a usable protocol element from an invalid construct. However, HTTP does not define
    330331   specific error handling mechanisms, except in cases where it has direct
    331332   impact on security. This is because different uses of the protocol require
     
    25072508      "Spurious 'MAY's"
    25082509    </t>
     2510    <t>
     2511      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
     2512      "ABNF requirements for recipients"
     2513    </t>
    25092514  </list>
    25102515</t>
Note: See TracChangeset for help on using the changeset viewer.