Ignore:
Timestamp:
Nov 28, 2012, 4:26:24 PM (7 years ago)
Author:
mnot@…
Message:

Rewrite changes from 2616

File:
1 edited

Legend:

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

    r2007 r2012  
    47194719<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    47204720<t>
    4721   Clarify that the string "HTTP" in the HTTP-version ABNF production is case
    4722   sensitive. Restrict the version numbers to be single digits due to the fact
    4723   that implementations are known to handle multi-digit version numbers
    4724   incorrectly.
     4721  The HTTP-version ABNF production has been clarified to be case-sensitive.
     4722  Additionally, version numbers has been restricted to single digits, due
     4723  to the fact that implementations are known to handle multi-digit version
     4724  numbers incorrectly.
    47254725  (<xref target="http.version"/>)
    47264726</t>
    47274727<t>
    4728   Take over the definition of "HTTPS" URI scheme, previously defined in
    4729   <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>.
     4728  The "HTTPS" URI scheme is now defined by this specification; previously,
     4729  it was done in  <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>.
    47304730  (<xref target="https.uri"/>)
    47314731</t>
    47324732<t>
    4733   Require that invalid whitespace around field-names be rejected.
    4734   Change ABNF productions for header fields to only define the field value.
     4733  Invalid whitespace around field-names is now required to be rejected,
     4734  because accepting it represents a security vulnerability.
     4735  (<xref target="header.fields"/>)
     4736</t>
     4737<t>
     4738  The ABNF productions defining header fields now only list the field value.
    47354739  (<xref target="header.fields"/>)
    47364740</t>
     
    47424746</t>
    47434747<t> 
    4744   The NUL octet is no longer allowed in comment and quoted-string
    4745   text. The quoted-pair rule no longer allows escaping control characters other than HTAB.
    4746   Non-ASCII content in header fields and reason phrase has been obsoleted and
    4747   made opaque (the TEXT rule was removed).
     4748  The NUL octet is no longer allowed in comment and quoted-string text.
    47484749  (<xref target="field.components"/>)
    4749 </t>
    4750 <t>
    4751   Require recipients to handle bogus "<x:ref>Content-Length</x:ref>" header
    4752   fields as errors.
     4750</t> 
     4751<t>
     4752  The quoted-pair rule no longer allows escaping control characters other than
     4753  HTAB.
     4754  (<xref target="field.components"/>)
     4755</t>
     4756<t>
     4757  Non-ASCII content in header fields and the reason phrase has been obsoleted
     4758  and made opaque (the TEXT rule was removed).
     4759  (<xref target="field.components"/>)
     4760</t>
     4761<t>
     4762  Bogus "<x:ref>Content-Length</x:ref>" header fields are now required to be
     4763  handled as errors by recipients.
    47534764  (<xref target="header.content-length"/>)
    47544765</t>
    47554766<t>
    4756   Remove reference to non-existent identity transfer-coding value tokens.
     4767  The "identity" transfer-coding value token has been removed.
    47574768  (Sections <xref format="counter" target="message.body"/> and
    47584769  <xref format="counter" target="transfer.codings"/>)
    47594770</t>
    47604771<t>
    4761   Remove special-case for "multipart/byteranges" in message body length
    4762   detection; add CONNECT as special case.
     4772  "multipart/byteranges" is no longer a way of determining message body length
     4773  detection.
    47634774  (<xref target="message.body.length"/>)
    47644775</t>
    47654776<t>
    4766   Clarification that the chunk length does not include the count of the octets
    4767   in the chunk header and trailer. Furthermore disallowed line folding
    4768   in chunk extensions, and deprecate their use.
     4777  CONNECT is a new, special case in determining message body length.
     4778  (<xref target="message.body.length"/>)
     4779</t>
     4780<t>
     4781  Chunk length does not include the count of the octets in the
     4782  chunk header and trailer.
    47694783  (<xref target="chunked.encoding"/>)
    47704784</t>
    47714785<t>
    4772   Update use of abs_path production from RFC 1808 to the path-absolute + query
    4773   components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
    4774   request method only.
     4786  Use of chunk extensions is deprecated, and line folding in them is
     4787  disallowed.
     4788  (<xref target="chunked.encoding"/>)
     4789</t>
     4790<t>
     4791  The path-absolute + query components of RFC3986 have been used to define the
     4792  request-target, instead of abs_path from RFC 1808.
    47754793  (<xref target="request-target"/>)
    47764794</t>
    47774795<t>
    4778   Clarify exactly when "close" connection options have to be sent; drop
    4779   notion of header fields being "hop-by-hop" without being listed in the
    4780   Connection header field.
     4796  The asterisk form of the request-target is only allowed in the OPTIONS
     4797  method.
     4798  (<xref target="request-target"/>)
     4799</t>
     4800<t>
     4801  Exactly when "close" connection options have to be sent has been clarified.
    47814802  (<xref target="header.connection"/>)
    47824803</t>
    4783 <t>
    4784   Remove hard limit of two connections per server.
    4785   Remove requirement to retry a sequence of requests as long it was idempotent.
    4786   Remove requirements about when servers are allowed to close connections
    4787   prematurely.
     4804<t> 
     4805  "hop-by-hop" header fields are required to appear in the Connection header
     4806  field; just because they're defined as hop-by-hop in this specification
     4807  doesn't exempt them.
     4808  (<xref target="header.connection"/>)
     4809</t>
     4810<t>
     4811  The limit of two connections per server has been removed.
    47884812  (<xref target="persistent.connections"/>)
    47894813</t>
    47904814<t>
    4791   Remove requirement to retry requests under certain circumstances when the
    4792   server prematurely closes the connection.
     4815  An idempotent sequence of requests is no longer required to be retried.
     4816  (<xref target="persistent.connections"/>)
     4817</t>
     4818<t>
     4819  The requirement to retry requests under certain circumstances when the
     4820  server prematurely closes the connection has been removed.
    47934821  (<xref target="persistent.reuse"/>)
    47944822</t>
    47954823<t>
    4796   Define the semantics of the <x:ref>Upgrade</x:ref> header field in responses
    4797   other than 101 (this was incorporated from <xref target="RFC2817"/>).
     4824  Some extraneous requirements about when servers are allowed to close
     4825  connections prematurely have been removed.
     4826  (<xref target="persistent.connections"/>)
     4827</t>
     4828<t>
     4829  The semantics of the <x:ref>Upgrade</x:ref> header field is now defined in
     4830  responses other than 101 (this was incorporated from <xref
     4831  target="RFC2817"/>).
    47984832  (<xref target="header.upgrade"/>)
    47994833</t>
     
    48034837</t>
    48044838<t>
    4805   Take over the Upgrade Token Registry, previously defined in
    4806   <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
     4839  This specification now defines the Upgrade Token Registry, previously
     4840  defined in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
    48074841  (<xref target="upgrade.token.registry"/>)
    48084842</t>
Note: See TracChangeset for help on using the changeset viewer.