Ignore:
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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1838 r1839  
    228228   document are to be interpreted as described in <xref target="RFC2119"/>.
    229229</t>
     230<t>
     231   Conformance criteria and considerations regarding error handling
     232   are defined in <xref target="conformance"/>.
     233</t>
    230234</section>
    231235
     
    609613</section>
    610614
    611 <section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
     615<section title="Conformance and Error Handling" anchor="conformance">
    612616<t>
    613617   This specification targets conformance criteria according to the role of
     
    21322136   since fragment identifiers are reserved for client-side processing
    21332137   (<xref target="RFC3986" x:fmt="," x:sec="3.5"/>).
    2134 </t>
    2135 <t>
    2136    HTTP intermediaries obtain the request semantics and target URI
    2137    from the request-line of an incoming request message.
    21382138</t>
    21392139</section>
Note: See TracChangeset for help on using the changeset viewer.