Changeset 2178

Timestamp:

06/02/13 09:10:24 (9 years ago)

Author:

julian.reschke@…

Message:

add some structure and dfn markup into request-target section

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (5 diffs)
• p1-messaging.xml (modified) (4 diffs)

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires August 5, 2013"; 
+       content: "Expires August 10, 2013"; 
   } 
   @bottom-right {
@@ -491 +491 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-02-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-02-06">
       <meta name="dct.replaces" content="urn:ietf:rfc:2145">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
@@ -520 +520 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">February 1, 2013</td>
+               <td class="right">February 6, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: August 5, 2013</td>
+               <td class="left">Expires: August 10, 2013</td>
                <td class="right"></td>
             </tr>
@@ -551 +551 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on August 5, 2013.</p>
+      <p>This Internet-Draft will expire on August 10, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1725 +1725 @@
   <a href="#asterisk-form" class="smpl">asterisk-form</a>  = "*"
 </pre><div id="origin-form">
-         <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> The most common form of request-target is the origin-form. When making a request directly to an origin server, other than
-            a CONNECT or server-wide OPTIONS request (as detailed below), a client <em class="bcp14">MUST</em> send only the absolute path and query components of the target URI as the request-target. If the target URI's path component
-            is empty, then the client <em class="bcp14">MUST</em> send "/" as the path within the origin-form of request-target. A <a href="#header.host" class="smpl">Host</a> header field is also sent, as defined in <a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section&nbsp;5.4</a>, containing the target URI's authority component (excluding any userinfo).
+         <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span>  <b>origin-form</b> 
          </p>
       </div>
-      <p id="rfc.section.5.3.p.4">For example, a client wishing to retrieve a representation of the resource identified as</p>
+      <p id="rfc.section.5.3.p.4">The most common form of request-target is the <dfn>origin-form</dfn>. When making a request directly to an origin server, other than a CONNECT or server-wide OPTIONS request (as detailed below),
+         a client <em class="bcp14">MUST</em> send only the absolute path and query components of the target URI as the request-target. If the target URI's path component
+         is empty, then the client <em class="bcp14">MUST</em> send "/" as the path within the origin-form of request-target. A <a href="#header.host" class="smpl">Host</a> header field is also sent, as defined in <a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section&nbsp;5.4</a>, containing the target URI's authority component (excluding any userinfo).
+      </p>
+      <p id="rfc.section.5.3.p.5">For example, a client wishing to retrieve a representation of the resource identified as</p>
       <div id="rfc.figure.u.38"></div><pre class="text">http://www.example.org/where?q=now
-</pre><p id="rfc.section.5.3.p.6">directly from the origin server would open (or reuse) a TCP connection to port 80 of the host "www.example.org" and send the
+</pre><p id="rfc.section.5.3.p.7">directly from the origin server would open (or reuse) a TCP connection to port 80 of the host "www.example.org" and send the
          lines:
       </p>
       <div id="rfc.figure.u.39"></div><pre class="text2">GET /where?q=now HTTP/1.1
 Host: www.example.org
-</pre><p id="rfc.section.5.3.p.8">followed by the remainder of the request message.</p>
+</pre><p id="rfc.section.5.3.p.9">followed by the remainder of the request message.</p>
       <div id="absolute-form">
-         <p id="rfc.section.5.3.p.9"><span id="rfc.iref.a.2"></span> When making a request to a proxy, other than a CONNECT or server-wide OPTIONS request (as detailed below), a client <em class="bcp14">MUST</em> send the target URI in absolute-form as the request-target. The proxy is requested to either service that request from a valid
-            cache, if possible, or make the same request on the client's behalf to either the next inbound proxy server or directly to
-            the origin server indicated by the request-target. Requirements on such "forwarding" of messages are defined in <a href="#message.forwarding" title="Message Forwarding">Section&nbsp;5.7</a>.
+         <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span>  <b>absolute-form</b> 
          </p>
       </div>
-      <p id="rfc.section.5.3.p.10">An example absolute-form of request-line would be:</p>
+      <p id="rfc.section.5.3.p.11">When making a request to a proxy, other than a CONNECT or server-wide OPTIONS request (as detailed below), a client <em class="bcp14">MUST</em> send the target URI in <dfn>absolute-form</dfn> as the request-target. The proxy is requested to either service that request from a valid cache, if possible, or make the
+         same request on the client's behalf to either the next inbound proxy server or directly to the origin server indicated by
+         the request-target. Requirements on such "forwarding" of messages are defined in <a href="#message.forwarding" title="Message Forwarding">Section&nbsp;5.7</a>.
+      </p>
+      <p id="rfc.section.5.3.p.12">An example absolute-form of request-line would be:</p>
       <div id="rfc.figure.u.40"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
-</pre><p id="rfc.section.5.3.p.12">To allow for transition to the absolute-form for all requests in some future version of HTTP, HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-form in requests, even though HTTP/1.1 clients will only send them in requests to proxies.
+</pre><p id="rfc.section.5.3.p.14">To allow for transition to the absolute-form for all requests in some future version of HTTP, HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-form in requests, even though HTTP/1.1 clients will only send them in requests to proxies.
       </p>
       <div id="authority-form">
-         <p id="rfc.section.5.3.p.13"><span id="rfc.iref.a.3"></span> The authority-form of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When making a CONNECT request to establish a tunnel through one or more proxies, a client <em class="bcp14">MUST</em> send only the target URI's authority component (excluding any userinfo) as the request-target. For example,
+         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span>  <b>authority-form</b> 
          </p>
       </div>
+      <p id="rfc.section.5.3.p.16">The <dfn>authority-form</dfn> of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When making a CONNECT request to establish a tunnel through one or more proxies, a client <em class="bcp14">MUST</em> send only the target URI's authority component (excluding any userinfo) as the request-target. For example,
+      </p>
       <div id="rfc.figure.u.41"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1
 </pre><div id="asterisk-form">
-         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.4"></span> The asterisk-form of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#Part2" id="rfc.xref.Part2.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When a client wishes to request OPTIONS for the server as a whole, as opposed to a specific named resource of that server,
-            the client <em class="bcp14">MUST</em> send only "*" (%x2A) as the request-target. For example,
+         <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span>  <b>asterisk-form</b> 
          </p>
       </div>
+      <p id="rfc.section.5.3.p.19">The <dfn>asterisk-form</dfn> of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#Part2" id="rfc.xref.Part2.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). When a client wishes to request OPTIONS for the server as a whole, as opposed to a specific named resource of that server,
+         the client <em class="bcp14">MUST</em> send only "*" (%x2A) as the request-target. For example,
+      </p>
       <div id="rfc.figure.u.42"></div><pre class="text2">OPTIONS * HTTP/1.1
-</pre><p id="rfc.section.5.3.p.17">If a proxy receives an OPTIONS request with an absolute-form of request-target in which the URI has an empty path and no query
+</pre><p id="rfc.section.5.3.p.21">If a proxy receives an OPTIONS request with an absolute-form of request-target in which the URI has an empty path and no query
          component, then the last proxy on the request chain <em class="bcp14">MUST</em> send a request-target of "*" when it forwards the request to the indicated origin server.
       </p>

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

@@ -2236 +2236 @@
 </artwork></figure>
 <t anchor="origin-form"><iref item="origin-form (of request-target)"/>
-   The most common form of request-target is the origin-form.
+  <x:h>origin-form</x:h>
+</t>
+<t>
+   The most common form of request-target is the <x:dfn>origin-form</x:dfn>.
    When making a request directly to an origin server, other than a CONNECT
    or server-wide OPTIONS request (as detailed below),
@@ -2266 +2269 @@
 </t>
 <t anchor="absolute-form"><iref item="absolute-form (of request-target)"/>
+  <x:h>absolute-form</x:h>
+</t>
+<t>
    When making a request to a proxy, other than a CONNECT or server-wide
    OPTIONS request (as detailed below), a client &MUST; send the target URI
-   in absolute-form as the request-target.
+   in <x:dfn>absolute-form</x:dfn> as the request-target.
    The proxy is requested to either service that request from a valid cache,
    if possible, or make the same request on the client's behalf to either
@@ -2288 +2294 @@
 </t>
 <t anchor="authority-form"><iref item="authority-form (of request-target)"/>
-   The authority-form of request-target is only used for CONNECT requests
+  <x:h>authority-form</x:h>
+</t>
+<t>
+   The <x:dfn>authority-form</x:dfn> of request-target is only used for CONNECT requests
    (&CONNECT;).  When making a CONNECT request to establish a tunnel through
    one or more proxies, a client &MUST; send only the target URI's
@@ -2298 +2307 @@
 </artwork></figure>
 <t anchor="asterisk-form"><iref item="asterisk-form (of request-target)"/>
-   The asterisk-form of request-target is only used for a server-wide
+  <x:h>asterisk-form</x:h>
+</t>
+<t>
+   The <x:dfn>asterisk-form</x:dfn> of request-target is only used for a server-wide
    OPTIONS request (&OPTIONS;).  When a client wishes to request OPTIONS
    for the server as a whole, as opposed to a specific named resource of