Ignore:
Timestamp:
03/06/13 06:24:51 (7 years ago)
Author:
fielding@…
Message:

Clarify that a recipient SHOULD process received messages in higher minor versions as if they were the highest minor version to wwhich the recipient is conformant; Clarify that 505 is for major version rejection; addresses #449

File:
1 edited

Legend:

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

    r2276 r2277  
    668668   (period or decimal point).  The first digit ("major version") indicates the
    669669   HTTP messaging syntax, whereas the second digit ("minor version") indicates
    670    the highest minor version to which the sender is
     670   the highest minor version within that major version to which the sender is
    671671   conformant and able to understand for future communication.  The minor
    672672   version advertises the sender's communication capabilities even when the
     
    721721</t>
    722722<t>
    723    An HTTP client &SHOULD; send a request version equal to the highest
     723   A client &SHOULD; send a request version equal to the highest
    724724   version to which the client is conformant and
    725725   whose major version is no higher than the highest version supported
    726    by the server, if this is known.  An HTTP client &MUST-NOT; send a
     726   by the server, if this is known.  A client &MUST-NOT; send a
    727727   version to which it is not conformant.
    728728</t>
    729729<t>
    730    An HTTP client &MAY; send a lower request version if it is known that
     730   A client &MAY; send a lower request version if it is known that
    731731   the server incorrectly implements the HTTP specification, but only
    732732   after the client has attempted at least one normal request and determined
     
    735735</t>
    736736<t>
    737    An HTTP server &SHOULD; send a response version equal to the highest
     737   A server &SHOULD; send a response version equal to the highest
    738738   version to which the server is conformant and
    739739   whose major version is less than or equal to the one received in the
    740    request.  An HTTP server &MUST-NOT; send a version to which it is not
     740   request.  A server &MUST-NOT; send a version to which it is not
    741741   conformant.  A server &MAY; send a <x:ref>505 (HTTP Version Not
    742742   Supported)</x:ref> response if it cannot send a response using the
     
    744744</t>
    745745<t>
    746    An HTTP server &MAY; send an HTTP/1.0 response to an HTTP/1.0 request
     746   A server &MAY; send an HTTP/1.0 response to a request
    747747   if it is known or suspected that the client incorrectly implements the
    748748   HTTP specification and is incapable of correctly processing later
     
    764764   <xref target="RFC2068"/> and <xref target="RFC2616"/>, and this revision
    765765   has specifically avoided any such changes to the protocol.
     766</t>
     767<t>
     768   When an HTTP message is received with a major version number that the
     769   recipient implements, but a higher minor version number than what the
     770   recipient implements, the recipient &SHOULD; process the message as if it
     771   were in the highest minor version within that major version to which the
     772   recipient is conformant. A recipient can assume that a message with a
     773   higher minor version, when sent to a recipient that has not yet indicated
     774   support for that higher version, is sufficiently backwards-compatible to be
     775   safely processed by any implementation of the same major version.
    766776</t>
    767777</section>
Note: See TracChangeset for help on using the changeset viewer.