Changeset 127
- Timestamp:
- 01/01/08 12:39:10 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r125 r127 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 1007 1007 a scheme name followed by a colon. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers 1008 (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",1009 "rel_path", and "authority" from that specification.1008 (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", 1009 "rel_path", "query", and "authority" from that specification. 1010 1010 </p> 1011 1011 <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> 2334 2334 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16</a>>: "Remove 'identity' token references" (<<a href="http://purl.org/NET/http-errata#identity">http://purl.org/NET/http-errata#identity</a>>) 2335 </li> 2336 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/26">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/26</a>>: "Import query BNF" 2335 2337 </li> 2336 2338 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42</a>>: "RFC2606 Compliance" -
draft-ietf-httpbis/latest/p1-messaging.xml
r125 r127 1008 1008 and <xref target="RFC1808"/>). This specification adopts the 1009 1009 definitions of "URI-reference", "absoluteURI", "relativeURI", "port", 1010 "host", "abs_path", "rel_path", and "authority" from that1010 "host", "abs_path", "rel_path", "query", and "authority" from that 1011 1011 specification. 1012 1012 </t> … … 4030 4030 </t> 4031 4031 <t> 4032 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/26"/>: 4033 "Import query BNF" 4034 </t> 4035 <t> 4032 4036 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42"/>: 4033 4037 "RFC2606 Compliance"
Note: See TracChangeset
for help on using the changeset viewer.