Changeset 2013 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 29/11/12 00:49:18 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1989 r2013 5652 5652 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616"> 5653 5653 <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). 5658 5659 (<xref target="header.content-location"/>) 5659 5660 </t> 5660 5661 <t> 5661 Clarify definition of POST.5662 The definition of POST has been clarified. 5662 5663 (<xref target="POST"/>) 5663 5664 </t> 5664 5665 <t> 5665 Remove requirement to handle all Content-* header fields; ban use of5666 <x:ref>Content-Range</x:ref> with PUT.5666 Servers are no longer required to handle all Content-* header fields in 5667 requests. 5667 5668 (<xref target="PUT"/>) 5668 5669 </t> 5669 5670 <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"/>. 5671 5677 (<xref target="CONNECT"/>) 5672 5678 </t> 5673 5679 <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). 5676 5683 (<xref target="header.max-forwards"/>) 5677 5684 </t> … … 5684 5691 </t> 5685 5692 <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. 5687 5695 (<xref target="header.accept-charset"/>) 5688 5696 </t> 5689 5697 <t> 5690 Allow "<x:ref>Referer</x:ref>" field value of "about:blank" as alternative to5691 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. 5692 5700 (<xref target="header.referer"/>) 5693 5701 </t> 5694 5702 <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. 5697 5705 (<xref target="status.203"/>) 5698 5706 </t> 5699 5707 <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. 5702 5711 (<xref target="status.3xx"/>) 5703 5712 </t> 5704 5713 <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 5709 5721 for status codes <x:ref>301</x:ref> and <x:ref>302</x:ref>. 5710 5722 (Sections <xref format="counter" target="status.301"/>, … … 5713 5725 </t> 5714 5726 <t> 5715 Deprecate <x:ref>305 (Use Proxy)</x:ref> status code, because user agents did5716 not implement it. It used to indicate that the target resource needs to be5717 accessed through the proxy given by the <x:ref>Location</x:ref> field. The5718 Location field gave the URI of the proxy. The recipient was expected to5719 repeat thissingle 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. 5720 5732 (<xref target="status.305"/>) 5721 5733 </t> 5722 5734 <t> 5723 Define status <x:ref>426 (Upgrade Required)</x:ref> (this wasincorporated5724 from <xref target="RFC2817"/> ).5735 The <x:ref>426 (Upgrade Required)</x:ref> status code has been incorporated 5736 from <xref target="RFC2817"/>. 5725 5737 (<xref target="status.426"/>) 5726 5738 </t> 5727 5739 <t> 5728 Correct syntax of "<x:ref>Location</x:ref>" header field to allow URI5729 references (including relative references and fragments), as referred symbol5730 "absoluteURI" wasn't what was expected, and add some clarifications as to5731 when use of fragments would not beappropriate.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. 5732 5744 (<xref target="header.location"/>) 5733 5745 </t> 5734 5746 <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. 5739 5749 (<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 5745 5759 &header-via;. 5746 5760 (<xref target="header.server"/>) 5747 5761 </t> 5748 5762 <t> 5749 Clarify contexts that charset is used in.5763 The contexts that charset is used in have been clarified. 5750 5764 (<xref target="charset"/>) 5751 5765 </t> 5752 5766 <t> 5753 Remove the default charset of "ISO-8859-1" for text media5754 t ypes; 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. 5755 5769 (<xref target="canonicalization.and.text.defaults"/>) 5756 5770 </t> 5757 5771 <t> 5758 Registration of Content Codings now requires IETF Review 5772 Registration of Content Codings now requires IETF Review. 5759 5773 (<xref target="content.coding.registry"/>) 5760 5774 </t> 5761 5775 <t> 5762 Remove definition of "Content-MD5 header" fieldbecause it was inconsistently5776 The Content-MD5 header field has been removed, because it was inconsistently 5763 5777 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. 5768 5783 (<xref target="method.registry"/>) 5769 5784 </t> 5770 5785 <t> 5771 T ake over the Status Code Registry, previously defined in5772 <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"/>. 5773 5788 (<xref target="status.code.registry"/>) 5774 5789 </t> 5775 5790 <t> 5776 Re move reference to non-existant identity transfer-coding value tokens.5791 References to the "identity" transfer-coding value token have been removed. 5777 5792 (<xref target="no.content-transfer-encoding"/>) 5778 5793 </t> 5779 5794 <t> 5780 Remove discussion of Content-Disposition header field, it is now defined5781 by <xreftarget="RFC6266"/>.5795 The Content-Disposition header field is now defined by <xref 5796 target="RFC6266"/>. 5782 5797 (<xref target="additional.features"/>) 5783 5798 </t>
Note: See TracChangeset
for help on using the changeset viewer.