Ignore:
Timestamp:
Jun 27, 2011, 4:39:35 AM (8 years ago)
Author:
julian.reschke@…
Message:

make HTTP version numbers single digits (see #273)

File:
1 edited

Legend:

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

    r1311 r1313  
    825825</t>
    826826<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-Version"/><iref primary="true" item="Grammar" subitem="HTTP-Prot-Name"/>
    827   <x:ref>HTTP-Version</x:ref>   = <x:ref>HTTP-Prot-Name</x:ref> "/" 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref>
     827  <x:ref>HTTP-Version</x:ref>   = <x:ref>HTTP-Prot-Name</x:ref> "/" <x:ref>DIGIT</x:ref> "." <x:ref>DIGIT</x:ref>
    828828  <x:ref>HTTP-Prot-Name</x:ref> = <x:abnf-char-sequence>"HTTP"</x:abnf-char-sequence> ; "HTTP", case-sensitive
    829829</artwork></figure>
    830830<t>
    831    The HTTP version number consists of two non-negative decimal integers
    832    separated by a "." (period or decimal point).  The first
    833    number ("major version") indicates the HTTP messaging syntax, whereas
    834    the second number ("minor version") indicates the highest minor
    835    version to which the sender is at least conditionally compliant and
    836    able to understand for future communication.  The minor version
    837    advertises the sender's communication capabilities even when the
     831   The HTTP version number consists of two decimal digits separated by a "."
     832   (period or decimal point).  The first digit ("major version") indicates the
     833   HTTP messaging syntax, whereas the second digit ("minor version") indicates
     834   the highest minor version to which the sender is at least conditionally
     835   compliant and able to understand for future communication.  The minor
     836   version advertises the sender's communication capabilities even when the
    838837   sender is only using a backwards-compatible subset of the protocol,
    839838   thereby letting the recipient know that more advanced features can
    840839   be used in response (by servers) or in future requests (by clients).
    841 </t>
    842 <t>
    843    When comparing HTTP versions, the numbers &MUST; be compared
    844    numerically rather than lexically.  For example, HTTP/2.4 is a lower
    845    version than HTTP/2.13, which in turn is lower than HTTP/12.3.
    846    Leading zeros &MUST; be ignored by recipients and &MUST-NOT; be sent.
    847840</t>
    848841<t>
     
    50115004</t>
    50125005<t>
    5013   Clarify that the string "HTTP" in the HTTP-Version ABNF production is case
    5014   sensitive.
     5006  Clarify that the string "HTTP" in the HTTP-Version ABFN production is case
     5007  sensitive. Restrict the version numbers to be single digits due to the fact
     5008  that implementations are known to handle multi-digit version numbers
     5009  incorrectly.
    50155010  (<xref target="http.version"/>)
    50165011</t>
     
    50765071
    50775072<x:ref>HTTP-Prot-Name</x:ref> = %x48.54.54.50 ; HTTP
    5078 <x:ref>HTTP-Version</x:ref> = HTTP-Prot-Name "/" 1*DIGIT "." 1*DIGIT
     5073<x:ref>HTTP-Version</x:ref> = HTTP-Prot-Name "/" DIGIT "." DIGIT
    50795074<x:ref>HTTP-date</x:ref> = rfc1123-date / obs-date
    50805075<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body
     
    58955890<section title="Since draft-ietf-httpbis-p1-messaging-14" anchor="changes.since.14">
    58965891<t>
    5897   None yet.
     5892  Closed issues:
     5893  <list style="symbols">
     5894    <t>
     5895      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/273"/>:
     5896      "HTTP-Version should be redefined as fixed length pair of DIGIT . DIGIT"
     5897    </t>
     5898  </list>
    58985899</t>
    58995900</section>
Note: See TracChangeset for help on using the changeset viewer.