Changeset 2607


Ignore:
Timestamp:
30/01/14 01:07:22 (6 years ago)
Author:
fielding@…
Message:

(editorial) change a MUST wait until X before interpreting request to a MUST NOT apply request until X; see #531

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2606 r2607  
    13091309               <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a href="#field.order">Field Order</a></h3>
    13101310               <p id="rfc.section.3.2.2.p.1">The order in which header fields with differing field names are received is not significant. However, it is good practice
    1311                   to send header fields that contain control data first, such as <a href="#header.host" class="smpl">Host</a> on requests and <a href="p2-semantics.html#header.date" class="smpl">Date</a> on responses, so that implementations can decide when not to handle a message as early as possible. A server <em class="bcp14">MUST</em> wait until the entire header section is received before interpreting a request message, since later header fields might include
    1312                   conditionals, authentication credentials, or deliberately misleading duplicate header fields that would impact request processing.
     1311                  to send header fields that contain control data first, such as <a href="#header.host" class="smpl">Host</a> on requests and <a href="p2-semantics.html#header.date" class="smpl">Date</a> on responses, so that implementations can decide when not to handle a message as early as possible. A server <em class="bcp14">MUST NOT</em> apply a request to the target resource until the entire request header section is received, since later header fields might
     1312                  include conditionals, authentication credentials, or deliberately misleading duplicate header fields that would impact request
     1313                  processing.
    13131314               </p>
    13141315               <p id="rfc.section.3.2.2.p.2">A sender <em class="bcp14">MUST NOT</em> generate multiple header fields with the same field name in a message unless either the entire field value for that header
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2606 r2607  
    12711271   header fields that contain control data first, such as <x:ref>Host</x:ref>
    12721272   on requests and <x:ref>Date</x:ref> on responses, so that implementations
    1273    can decide when not to handle a message as early as possible.  A server
    1274    &MUST; wait until the entire header section is received before interpreting
    1275    a request message, since later header fields might include conditionals,
    1276    authentication credentials, or deliberately misleading duplicate
    1277    header fields that would impact request processing.
     1273   can decide when not to handle a message as early as possible.
     1274   A server &MUST-NOT; apply a request to the target resource until the entire
     1275   request header section is received, since later header fields might include
     1276   conditionals, authentication credentials, or deliberately misleading
     1277   duplicate header fields that would impact request processing.
    12781278</t>
    12791279<t>
Note: See TracChangeset for help on using the changeset viewer.