Changeset 2024 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 29/11/12 23:51:24 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r2012 r2024 4719 4719 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616"> 4720 4720 <t> 4721 HTTP's approach to error handling has been explained. 4722 (<xref target="conformance"/>) 4723 </t> 4724 <t> 4725 The expectation to support HTTP/0.9 requests has been removed. 4726 </t> 4727 <t> 4728 The term "Effective Request URI" has been introduced. 4729 (<xref target="effective.request.uri" />) 4730 </t> 4731 <t> 4732 HTTP messages can be (and often are) buffered by implementations; despite 4733 it sometimes being available as a stream, HTTP is fundamentally a 4734 message-oriented protocol. 4735 (<xref target="http.message" />) 4736 </t> 4737 <t> 4738 Minimum supported sizes for various protocol elements have been 4739 suggested, to improve interoperability. 4740 </t> 4741 <t> 4742 Header fields that span multiple lines ("line folding") are deprecated. 4743 (<xref target="field.parsing" />) 4744 </t> 4745 <t> 4721 4746 The HTTP-version ABNF production has been clarified to be case-sensitive. 4722 4747 Additionally, version numbers has been restricted to single digits, due … … 4726 4751 </t> 4727 4752 <t> 4728 The "HTTPS"URI scheme is now defined by this specification; previously,4753 The HTTPS URI scheme is now defined by this specification; previously, 4729 4754 it was done in <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>. 4730 4755 (<xref target="https.uri"/>) 4756 </t> 4757 <t> 4758 The HTTPS URI scheme implies end-to-end security. 4759 (<xref target="https.uri"/>) 4760 </t> 4761 <t> 4762 Userinfo (i.e., username and password) are now disallowed in HTTP and 4763 HTTPS URIs, because of security issues related to their transmission on the 4764 wire. 4765 (<xref target="http.uri" />) 4731 4766 </t> 4732 4767 <t> … … 4746 4781 </t> 4747 4782 <t> 4748 The NUL octet is no longer allowed in comment and quoted-string text. 4783 The NUL octet is no longer allowed in comment and quoted-string text, and 4784 handling of backslash-escaping in them has been clarified. 4749 4785 (<xref target="field.components"/>) 4750 4786 </t> … … 4768 4804 (Sections <xref format="counter" target="message.body"/> and 4769 4805 <xref format="counter" target="transfer.codings"/>) 4806 </t> 4807 <t> 4808 The algorithm for determining the message body length has been clarified 4809 to indicate all of the special cases (e.g., driven by methods or status 4810 codes) that affect it, and that new protocol elements cannot define such 4811 special cases. 4812 (<xref target="message.body.length"/>) 4770 4813 </t> 4771 4814 <t> … … 4837 4880 </t> 4838 4881 <t> 4882 The meaning of the "deflate" content coding has been clarified. 4883 (<xref target="deflate.coding" />) 4884 </t> 4885 <t> 4839 4886 This specification now defines the Upgrade Token Registry, previously 4840 4887 defined in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>. … … 4842 4889 </t> 4843 4890 <t> 4844 Empty list elements in list productions have been deprecated. 4891 Empty list elements in list productions (e.g., a list header containing 4892 ", ,") have been deprecated. 4845 4893 (<xref target="abnf.extension"/>) 4894 </t> 4895 <t> 4896 Issues with the Keep-Alive and Proxy-Connection headers in requests 4897 are pointed out, with use of the latter being discouraged altogether. 4898 (<xref target="compatibility.with.http.1.0.persistent.connections" />) 4846 4899 </t> 4847 4900 </section>
Note: See TracChangeset
for help on using the changeset viewer.