Ignore:
Timestamp:
Jul 9, 2012, 1:35:28 AM (7 years ago)
Author:
fielding@…
Message:

fix [1682] so that it takes roles into consideration (#361)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1744 r1747  
    600600   on senders, recipients, clients, servers, user agents, intermediaries,
    601601   origin servers, proxies, gateways, or caches, depending on what behavior
    602    is being constrained by the requirement.
     602   is being constrained by the requirement. The verb "generate" is used
     603   instead of "send" where a requirement differentiates between creating a
     604   protocol element and merely forwarding a received element downstream.
    603605</t>
    604606<t>
     
    607609</t>
    608610<t>
    609    Senders &MUST-NOT; generate protocol elements that do not match the grammar
    610    defined by the ABNF rules for those protocol elements.
    611 </t>
    612 <t>
    613    Unless noted otherwise, recipients &MUST; be able to parse all protocol
    614    elements matching the ABNF rules defined for them and &MAY; attempt to recover a usable
     611   A sender &MUST-NOT; generate protocol elements that do not match
     612   the grammar defined by the ABNF rules for those protocol elements that
     613   are applicable to the sender's role.
     614   If a received protocol element is processed, the recipient &MUST; be able
     615   to parse any value that would match the ABNF rules for that protocol
     616   element, excluding only those rules not applicable to the recipient's role.
     617</t>
     618<t>
     619   Unless noted otherwise, a recipient &MAY; attempt to recover a usable
    615620   protocol element from an invalid construct.  HTTP does not define
    616621   specific error handling mechanisms except when they have a direct impact
     
    10191024</artwork></figure>
    10201025<t>
    1021 </t>
    1022 <t>
    10231026   Implementations &MUST-NOT; send whitespace between the start-line and
    10241027   the first header field. The presence of such whitespace in a request
     
    10421045  <x:ref>request-line</x:ref>   = <x:ref>method</x:ref> <x:ref>SP</x:ref> <x:ref>request-target</x:ref> <x:ref>SP</x:ref> <x:ref>HTTP-version</x:ref> <x:ref>CRLF</x:ref>
    10431046</artwork></figure>
     1047<t>
     1048   A server &MUST; be able to parse any received message that begins
     1049   with a request-line and matches the ABNF rule for HTTP-message.
     1050</t>
    10441051<iref primary="true" item="method"/>
    10451052<t anchor="method">
     
    11051112  <x:ref>status-line</x:ref> = <x:ref>HTTP-version</x:ref> <x:ref>SP</x:ref> <x:ref>status-code</x:ref> <x:ref>SP</x:ref> <x:ref>reason-phrase</x:ref> <x:ref>CRLF</x:ref>
    11061113</artwork></figure>
     1114<t>
     1115   A client &MUST; be able to parse any received message that begins
     1116   with a status-line and matches the ABNF rule for HTTP-message.
     1117</t>
    11071118
    11081119<t anchor="status-code">
Note: See TracChangeset for help on using the changeset viewer.