Ignore:
Timestamp:
Nov 28, 2012, 8:28:13 PM (7 years ago)
Author:
mnot@…
Message:

Update Changes from RFC2626, from issues list.

File:
1 edited

Legend:

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

    r2013 r2023  
    56785678</t>
    56795679<t>
    5680   The "<x:ref>Max-Forwards</x:ref>" header field is now restricted to the
     5680  The requirements upon and semantics of CONNECT request and response bodies
     5681  have been clarified.
     5682  (<xref target="CONNECT"/>)
     5683</t>
     5684<t>
     5685  The <x:ref>OPTIONS</x:ref> and <x:ref>TRACE</x:ref> request methods are
     5686  now defined as being safe.
     5687  (<xref target="OPTIONS"/> and <xref target="TRACE"/>)
     5688</t>
     5689<t>
     5690  The <x:ref>Max-Forwards</x:ref> header field is now restricted to the
    56815691  OPTIONS and TRACE methods (previously, extension methods could have used it
    56825692  as well).
     
    56965706</t>
    56975707<t>
    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.
     5708  The <x:ref>Referer</x:ref> header field can now have a value of
     5709  "about:blank" as an alternative to not sending a Referer header field.
    57005710  (<xref target="header.referer"/>)
     5711</t>
     5712<t>
     5713  The <x:ref>201 (Created)</x:ref> status code can indicate that more than
     5714  one resource has been created (as well as just one).
    57015715</t>
    57025716<t>
     
    57165730  based upon the request method semantics.
    57175731  (<xref target="status.3xx"/>)
     5732</t>
     5733<t>
     5734  The syntax of the <x:ref>Location</x:ref> header field has been corrected
     5735  to allow URI references (including relative references and fragments), along
     5736  with some clarifications as to when use of fragments would not be
     5737  appropriate.
     5738  (<xref target="header.location"/>)
     5739</t>
     5740<t>
     5741  The 303 (See Other) status code is now cacheable, if explicit freshness
     5742  information is available.
     5743  (<xref target="status.303" />)
    57185744</t>
    57195745<t>
     
    57335759</t>
    57345760<t>
     5761  The <x:ref>400 (Bad Request)</x:ref> status code has been made more generic;
     5762  it isn't limited to syntax errors.
     5763  (<xref target="status.400"/>)
     5764</t>
     5765<t>
     5766  The <x:ref>403 (Forbidden)</x:ref> status code has been clarified,
     5767  especially with regards to authentication.
     5768  (<xref target="status.403"/>)
     5769</t>
     5770<t>
    57355771  The <x:ref>426 (Upgrade Required)</x:ref> status code has been incorporated
    57365772  from <xref target="RFC2817"/>.
    57375773  (<xref target="status.426"/>)
    5738 </t>
    5739 <t>
    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.
    5744   (<xref target="header.location"/>)
    57455774</t>
    57465775<t>
Note: See TracChangeset for help on using the changeset viewer.