Changeset 127

Timestamp:

01/01/08 12:39:10 (14 years ago)

Author:

julian.reschke@…

Message:

Resolve #26: note that we're using "query" as defined in RFC2396, also fix missing whitespace.

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -1006 +1006 @@
       <p id="rfc.section.3.2.1.p.1">URIs in HTTP can be represented in absolute form or relative to some known base URI <a href="#RFC1808" id="rfc.xref.RFC1808.1"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>, depending upon the context of their use. The two forms are differentiated by the fact that absolute URIs always begin with
          a scheme name followed by a colon. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers
-         (URI): Generic Syntax and Semantics," <a href="#RFC2396" id="rfc.xref.RFC2396.1"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> (which replaces <a href="#RFC1738" id="rfc.xref.RFC1738.3"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and <a href="#RFC1808" id="rfc.xref.RFC1808.2"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>). This specification adopts the definitions of "URI-reference", "absoluteURI", "relativeURI", "port", "host","abs_path",
-         "rel_path", and "authority" from that specification.
+         (URI): Generic Syntax and Semantics," <a href="#RFC2396" id="rfc.xref.RFC2396.1"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> (which replaces <a href="#RFC1738" id="rfc.xref.RFC1738.3"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and <a href="#RFC1808" id="rfc.xref.RFC1808.2"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>). This specification adopts the definitions of "URI-reference", "absoluteURI", "relativeURI", "port", "host", "abs_path",
+         "rel_path", "query", and "authority" from that specification.
       </p>
       <p id="rfc.section.3.2.1.p.2">The HTTP protocol does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="p2-semantics.html#status.414" title="414 Request-URI Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
@@ -2333 +2333 @@
          </li>
          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16</a>&gt;: "Remove 'identity' token references" (&lt;<a href="http://purl.org/NET/http-errata#identity">http://purl.org/NET/http-errata#identity</a>&gt;)
+         </li>
+         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/26">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/26</a>&gt;: "Import query BNF"
          </li>
          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42</a>&gt;: "RFC2606 Compliance"

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

@@ -1008 +1008 @@
    and <xref target="RFC1808"/>). This specification adopts the
    definitions of "URI-reference", "absoluteURI", "relativeURI", "port",
-   "host","abs_path", "rel_path", and "authority" from that
+   "host", "abs_path", "rel_path", "query", and "authority" from that
    specification.
 </t>
@@ -4030 +4030 @@
     </t>
     <t>
+      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/26"/>:
+      "Import query BNF"
+    </t>
+    <t>
       <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42"/>:
       "RFC2606 Compliance"