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

Timestamp:

06/07/09 09:50:26 (13 years ago)

Author:

julian.reschke@…

Message:

Take out language that implied that there may be methods for which a request body MUST NOT be included (related to #88)

File:

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

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

@@ -32 +32 @@
   <!ENTITY request-header-fields  "<xref target='Part2' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY response-header-fields "<xref target='Part2' x:rel='#response.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY method                 "<xref target='Part2' x:rel='#method' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -1378 +1377 @@
    The presence of a message-body in a request is signaled by the
    inclusion of a Content-Length or Transfer-Encoding header field in
-   the request's message-headers. A message-body &MUST-NOT; be included in
-   a request if the specification of the request method (&method;)
-   explicitly disallows an entity-body in requests.
+   the request's message-headers. 
    When a request message contains both a message-body of non-zero
    length and a method that does not define any semantics for that
@@ -4952 +4949 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/88"/>:
+      "205 Bodies" (took out language that implied that there may be
+      methods for which a request body MUST NOT be included)
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/163"/>:
       "editorial improvements around HTTP-date"