Changeset 1839 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

Aug 25, 2012, 2:08:32 AM (7 years ago)

Author:

fielding@…

Message:

Begin plowing through p2 to properly explain what HTTP semantics are and why.
Rewrite introductory description of methods.
Rewrite definition of "safe" to be more operable and weaken the original
same-origin restrictions to be more consistent with modern UAs.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -228 +228 @@
    document are to be interpreted as described in <xref target="RFC2119"/>.
 </t>
+<t>
+   Conformance criteria and considerations regarding error handling
+   are defined in <xref target="conformance"/>.
+</t>
 </section>
 
@@ -609 +613 @@
 </section>
 
-<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
+<section title="Conformance and Error Handling" anchor="conformance">
 <t>
    This specification targets conformance criteria according to the role of
@@ -2132 +2136 @@
    since fragment identifiers are reserved for client-side processing
    (<xref target="RFC3986" x:fmt="," x:sec="3.5"/>).
-</t>
-<t>
-   HTTP intermediaries obtain the request semantics and target URI
-   from the request-line of an incoming request message.
 </t>
 </section>