Changeset 2013


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

Clean up Changes from RFC2616; partially addresses #419.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1989 r2013  
    56525652<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    56535653<t>
    5654   Remove base URI setting semantics for "<x:ref>Content-Location</x:ref>" due to
    5655   poor implementation support (which was caused by too many broken servers emitting
    5656   bogus Content-Location header fields, and also the potentially undesirable effect
    5657   of potentially breaking relative links in content-negotiated resources).
     5654  <x:ref>Content-Location</x:ref> no longer sets a base URI, due to poor
     5655  implementation support (which was caused by too many broken servers emitting
     5656  bogus Content-Location header fields, and also the potentially undesirable
     5657  effect of potentially breaking relative links in content-negotiated
     5658  resources).
    56585659  (<xref target="header.content-location"/>)
    56595660</t>
    56605661<t>
    5661   Clarify definition of POST.
     5662  The definition of POST has been clarified.
    56625663  (<xref target="POST"/>)
    56635664</t>
    56645665<t>
    5665   Remove requirement to handle all Content-* header fields; ban use of
    5666   <x:ref>Content-Range</x:ref> with PUT.
     5666  Servers are no longer required to handle all Content-* header fields in
     5667  requests.
    56675668  (<xref target="PUT"/>)
    56685669</t>
    56695670<t>
    5670   Take over definition of CONNECT method from <xref target="RFC2817"/>.
     5671  Use of <x:ref>Content-Range</x:ref> is explicitly banned on PUT requests.
     5672  (<xref target="PUT"/>)
     5673</t>
     5674<t>
     5675  The CONNECT method is now defined by this specification, taking over from
     5676  <xref target="RFC2817"/>.
    56715677  (<xref target="CONNECT"/>)
    56725678</t>
    56735679<t>
    5674   Restrict "<x:ref>Max-Forwards</x:ref>" header field to OPTIONS and TRACE
    5675   (previously, extension methods could have used it as well).
     5680  The "<x:ref>Max-Forwards</x:ref>" header field is now restricted to the
     5681  OPTIONS and TRACE methods (previously, extension methods could have used it
     5682  as well).
    56765683  (<xref target="header.max-forwards"/>)
    56775684</t>
     
    56845691</t>
    56855692<t>
    5686   Remove ISO-8859-1 special-casing in <x:ref>Accept-Charset</x:ref>.
     5693  Special casing for ISO-8859-1 in <x:ref>Accept-Charset</x:ref> has been
     5694  removed.
    56875695  (<xref target="header.accept-charset"/>)
    56885696</t>
    56895697<t>
    5690   Allow "<x:ref>Referer</x:ref>" field value of "about:blank" as alternative to
    5691   not specifying it.
     5698  "<x:ref>Referer</x:ref>" can now hoave a field value of "about:blank" as an
     5699  alternative to not sending a Referer header field.
    56925700  (<xref target="header.referer"/>)
    56935701</t>
    56945702<t>
    5695   Broadened the definition of <x:ref>203 (Non-Authoritative Information)</x:ref>
    5696   to include cases of payload transformations as well.
     5703  The definition of <x:ref>203 (Non-Authoritative Information)</x:ref> has
     5704  been broadened to include cases of payload transformations as well.
    56975705  (<xref target="status.203"/>)
    56985706</t>
    56995707<t>
    5700   Status codes <x:ref>301</x:ref>, <x:ref>302</x:ref>, and <x:ref>307</x:ref>:
    5701   removed the normative requirements on both response payloads and user interaction.
     5708  Redirect status codes <x:ref>301</x:ref>, <x:ref>302</x:ref>, and
     5709  <x:ref>307</x:ref> no longer have normative requirements on response
     5710  payloads and user interaction.
    57025711  (<xref target="status.3xx"/>)
    57035712</t>
    57045713<t>
    5705   Failed to consider that there are many other request methods that are safe
    5706   to automatically redirect, and further that the user agent is able to make
    5707   that determination based on the request method semantics.
    5708   Furthermore, allow user agents to rewrite the method from POST to GET
     5714  The request methods that are safe to automatically redirect is no
     5715  longer a closed set; user agents are able to make that determination
     5716  based upon the request method semantics.
     5717  (<xref target="status.3xx"/>)
     5718</t>
     5719<t>
     5720  User agents are now allowed to rewrite the method from POST to GET
    57095721  for status codes <x:ref>301</x:ref> and <x:ref>302</x:ref>.
    57105722  (Sections <xref format="counter" target="status.301"/>,
     
    57135725</t>
    57145726<t>
    5715   Deprecate <x:ref>305 (Use Proxy)</x:ref> status code, because user agents did
    5716   not implement it. It used to indicate that the target resource needs to be
    5717   accessed through the proxy given by the <x:ref>Location</x:ref> field. The
    5718   Location field gave the URI of the proxy. The recipient was expected to
    5719   repeat this single request via the proxy.
     5727  The <x:ref>305 (Use Proxy)</x:ref> status code is now deprecated, because
     5728  user agents did not implement it. It used to indicate that the target
     5729  resource needed to be accessed through the proxy given by the
     5730  <x:ref>Location</x:ref> field. The recipient was expected to repeat this
     5731  single request via the proxy.
    57205732  (<xref target="status.305"/>)
    57215733</t>
    57225734<t>
    5723   Define status <x:ref>426 (Upgrade Required)</x:ref> (this was incorporated
    5724   from <xref target="RFC2817"/>).
     5735  The <x:ref>426 (Upgrade Required)</x:ref> status code has been incorporated
     5736  from <xref target="RFC2817"/>.
    57255737  (<xref target="status.426"/>)
    57265738</t>
    57275739<t>
    5728   Correct syntax of "<x:ref>Location</x:ref>" header field to allow URI
    5729   references (including relative references and fragments), as referred symbol
    5730   "absoluteURI" wasn't what was expected, and add some clarifications as to
    5731   when use of fragments would not be appropriate.
     5740  The syntax of the <x:ref>Location</x:ref> header field has been corrected
     5741  to allow URI references (including relative references and fragments), along
     5742  with some clarifications as to when use of fragments would not be
     5743  appropriate.
    57325744  (<xref target="header.location"/>)
    57335745</t>
    57345746<t>
    5735   Reclassify "<x:ref>Allow</x:ref>" as response header field, removing the
    5736   option to specify it in a PUT request.
    5737   Relax the server requirement on the contents of the Allow header field and
    5738   remove requirement on clients to always trust the header field value.
     5747  <x:ref>Allow</x:ref> has been reclassified as a response header field,
     5748  removing the option to specify it in a PUT request.
    57395749  (<xref target="header.allow"/>)
    5740 </t>
    5741 <t>
    5742   In the description of the "<x:ref>Server</x:ref>" header field, the
    5743   "<x:ref>Via</x:ref>" field was described as a SHOULD. The requirement was and
    5744   is stated correctly in the description of the Via header field in
     5750</t> 
     5751<t> 
     5752  Requirements relating to the content of the Allow header have been relaxed;
     5753  correspondingly, clients are not required to always trust its value.
     5754  (<xref target="header.allow"/>)
     5755</t>
     5756<t>
     5757  The requirement to produce a <x:ref>Via</x:ref> header field has been moved
     5758  from the description of the <x:ref>Server</x:ref> header field to
    57455759  &header-via;.
    57465760  (<xref target="header.server"/>)
    57475761</t>
    57485762<t>
    5749   Clarify contexts that charset is used in.
     5763  The contexts that charset is used in have been clarified.
    57505764  (<xref target="charset"/>)
    57515765</t>
    57525766<t>
    5753   Remove the default charset of "ISO-8859-1" for text media
    5754   types; the default now is whatever the media type definition says.
     5767  The default charset of "ISO-8859-1" for text media types has been removed;
     5768  the default now is whatever the media type definition says.
    57555769  (<xref target="canonicalization.and.text.defaults"/>)
    57565770</t>
    57575771<t>
    5758   Registration of Content Codings now requires IETF Review
     5772  Registration of Content Codings now requires IETF Review.
    57595773  (<xref target="content.coding.registry"/>)
    57605774</t>
    57615775<t>
    5762   Remove definition of "Content-MD5 header" field because it was inconsistently
     5776  The Content-MD5 header field has been removed, because it was inconsistently
    57635777  implemented with respect to partial responses, and also because of known
    5764   deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details).
    5765 </t>
    5766 <t>
    5767   Introduce Method Registry.
     5778  deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for
     5779  details).
     5780</t>
     5781<t>
     5782  This specification introduces a Method Registry.
    57685783  (<xref target="method.registry"/>)
    57695784</t>
    57705785<t>
    5771   Take over the Status Code Registry, previously defined in
    5772   <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>.
     5786  The Status Code Registry is now defined by this specification; previously,
     5787  it was defined in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>.
    57735788  (<xref target="status.code.registry"/>)
    57745789</t>
    57755790<t>
    5776   Remove reference to non-existant identity transfer-coding value tokens.
     5791  References to the "identity" transfer-coding value token have been removed.
    57775792  (<xref target="no.content-transfer-encoding"/>)
    57785793</t>
    57795794<t>
    5780   Remove discussion of Content-Disposition header field, it is now defined
    5781   by <xref target="RFC6266"/>.
     5795  The Content-Disposition header field is now defined by <xref
     5796  target="RFC6266"/>.
    57825797  (<xref target="additional.features"/>)
    57835798</t>
Note: See TracChangeset for help on using the changeset viewer.