Changeset 1054

Timestamp:

23/10/10 08:00:32 (12 years ago)

Author:

julian.reschke@…

Message:

The asterisk form is only allowed for OPTIONS (see #233)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (3 diffs)
• p1-messaging.xml (modified) (3 diffs)

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

@@ -1341 +1341 @@
                  / <a href="#uri" class="smpl">authority</a>
 </pre><p id="rfc.section.4.1.2.p.3">The four options for request-target are dependent on the nature of the request.</p>
-      <p id="rfc.section.4.1.2.p.4"><span id="rfc.iref.a.1"></span> The asterisk "*" ("asterisk form") means that the request does not apply to a particular resource, but to the server itself,
-         and is only allowed when the method used does not necessarily apply to a resource. One example would be
+      <p id="rfc.section.4.1.2.p.4"><span id="rfc.iref.a.1"></span> The asterisk "*" ("asterisk form") means that the request does not apply to a particular resource, but to the server itself.
+         This is only allowed for the OPTIONS method. Thus, the only valid example is
       </p>
       <div id="rfc.figure.u.35"></div><pre class="text2">OPTIONS * HTTP/1.1
@@ -2971 +2971 @@
       <p id="rfc.section.B.3.p.6">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">6.2</a>)
       </p>
-      <p id="rfc.section.B.3.p.7">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. (<a href="#request-target" title="request-target">Section&nbsp;4.1.2</a>)
+      <p id="rfc.section.B.3.p.7">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk
+         form is allowed for the OPTIONS method only. (<a href="#request-target" title="request-target">Section&nbsp;4.1.2</a>)
       </p>
       <p id="rfc.section.B.3.p.8">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore
@@ -3473 +3474 @@
       <ul>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/193">http://tools.ietf.org/wg/httpbis/trac/ticket/193</a>&gt;: "Trailer requirements"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/233">http://tools.ietf.org/wg/httpbis/trac/ticket/233</a>&gt;: "Is * usable as a request-uri for new methods?"
          </li>
       </ul>

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

@@ -1514 +1514 @@
 <t><iref item="asterisk form (of request-target)"/>
    The asterisk "*" ("asterisk form") means that the request does not apply to a
-   particular resource, but to the server itself, and is only allowed
-   when the method used does not necessarily apply to a resource. One
-   example would be
+   particular resource, but to the server itself. This is only allowed for the
+   OPTIONS method. Thus, the only valid example is
 </t>
 <figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
@@ -4875 +4874 @@
 <t>
   Update use of abs_path production from RFC 1808 to the path-absolute + query
-  components of RFC 3986.
+  components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
+  method only.
   (<xref target="request-target"/>)
 </t>
@@ -5689 +5689 @@
       "Trailer requirements"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/233"/>:
+      "Is * usable as a request-uri for new methods?"
+    </t>
   </list>
 </t>