Ticket #361: 361.diff

File 361.diff, 1.3 KB (added by julian.reschke@…, 7 years ago)

Proposed patch for P2; needs more changes for the other parts.

  • p2-semantics.xml

     
    301301   upon them, Senders &MUST-NOT; generate protocol elements that are invalid.
    302302</t>
    303303<t>
    304    Unless noted otherwise, Recipients &MAY; take steps to recover a usable
    305    protocol element from an invalid construct. However, HTTP does not define
     304   Unless noted otherwise, Recipients &MUST; be able to parse all protocol
     305   elements matching the ABNF rules defined for them and &MAY; take steps to
     306   recover a usable protocol element from an invalid construct. However, HTTP does not define
    306307   specific error handling mechanisms, except in cases where it has direct
    307308   impact on security. This is because different uses of the protocol require
    308309   different error handling strategies; for example, a Web browser may wish to
     
    67816782
    67826783<section title="Since draft-ietf-httpbis-p3-payload-19" anchor="changes.3.since.19">
    67836784<t>
    6784   None yet.
     6785  Closed issues:
     6786  <list style="symbols">
     6787    <t>
     6788      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
     6789      "ABNF requirements for recipients"
     6790    </t>
     6791  </list>
    67856792</t>
    67866793</section>
    67876794</section>