Changeset 1063 for draft-ietf-httpbis

Timestamp:

27/10/10 09:42:28 (9 years ago)

Author:

julian.reschke@…

Message:

use a consistent style to define the four forms of request targets

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (6 diffs)
• p1-messaging.xml (modified) (2 diffs)

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

@@ -404 +404 @@
       <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="2010-10-25">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-10-27">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
@@ -435 +435 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 28, 2011</td>
+               <td class="left">Expires: April 30, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -488 +488 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 25, 2010</td>
+               <td class="right">October 27, 2010</td>
             </tr>
          </tbody>
@@ -516 +516 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 28, 2011.</p>
+      <p>This Internet-Draft will expire on April 30, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1345 +1345 @@
       </p>
       <div id="rfc.figure.u.35"></div><pre class="text2">OPTIONS * HTTP/1.1
-</pre><p id="rfc.section.4.1.2.p.6"><span id="rfc.iref.a.2"></span> The absolute-URI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,
+</pre><p id="rfc.section.4.1.2.p.6"><span id="rfc.iref.a.2"></span> The "absolute-URI" form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,
          and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absolute-URI. In order to avoid request
          loops, a proxy <em class="bcp14">MUST</em> be able to recognize all of its server names, including any aliases, local variations, and the numeric IP address. An example
@@ -1353 +1353 @@
 </pre><p id="rfc.section.4.1.2.p.8">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
       </p>
-      <p id="rfc.section.4.1.2.p.9"><span id="rfc.iref.a.3"></span> The authority form is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 7.9</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
+      <p id="rfc.section.4.1.2.p.9"><span id="rfc.iref.a.3"></span> The "authority form" is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 7.9</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
       </p>
       <p id="rfc.section.4.1.2.p.10"><span id="rfc.iref.p.2"></span> The most common form of request-target is that used to identify a resource on an origin server or gateway ("path-absolute

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

@@ -1521 +1521 @@
 </artwork></figure>
 <t><iref item="absolute-URI form (of request-target)"/>
-   The absolute-URI form is &REQUIRED; when the request is being made to a
+   The "absolute-URI" form is &REQUIRED; when the request is being made to a
    proxy. The proxy is requested to forward the request or service it
    from a valid cache, and return the response. Note that the proxy &MAY;
@@ -1540 +1540 @@
 </t>
 <t><iref item="authority form (of request-target)"/>
-   The authority form is only used by the CONNECT method (&CONNECT;).
+   The "authority form" is only used by the CONNECT method (&CONNECT;).
 </t>
 <t><iref item="path-absolute form (of request-target)"/>