Changeset 173
- Timestamp:
- 24/01/08 12:46:28 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r172 r173 1017 1017 a scheme name followed by a colon. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers 1018 1018 (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", 1019 " rel_path", "query", and "authority" from that specification.1019 "query", and "authority" from that specification. 1020 1020 </p> 1021 1021 <p id="rfc.section.3.2.1.p.2">HTTP 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>). … … 2445 2445 <ul> 2446 2446 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19</a>>: "Bodies on GET (and other) requests" 2447 </li> 2448 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82</a>>: "rel_path not used" 2447 2449 </li> 2448 2450 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r172 r173 1027 1027 and <xref target="RFC1808"/>). This specification adopts the 1028 1028 definitions of "URI-reference", "absoluteURI", "relativeURI", "port", 1029 "host", "abs_path", "rel_path", "query", and "authority" from that 1030 specification. 1029 "host", "abs_path", "query", and "authority" from that specification. 1031 1030 </t> 1032 1031 <t> … … 4167 4166 "Bodies on GET (and other) requests" 4168 4167 </t> 4168 <t> 4169 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82"/>: 4170 "rel_path not used" 4171 </t> 4169 4172 </list> 4170 4173 </t> -
draft-ietf-httpbis/latest/p6-cache.html
r172 r173 1146 1146 expected to observe an origin server's explicit restrictions on caching. 1147 1147 </p> 1148 <p id="rfc.section.10.p.2">We note one exception to this rule: since some applications have traditionally used GET s and HEADs with query URLs (those1149 containing a "?" in the rel_path part)to perform operations with significant side effects, caches <em class="bcp14">MUST NOT</em> treat responses to such URIs as fresh unless the server provides an explicit expiration time. This specifically means that1148 <p id="rfc.section.10.p.2">We note one exception to this rule: since some applications have traditionally used GET and HEAD requests with URLs containing 1149 a query part to perform operations with significant side effects, caches <em class="bcp14">MUST NOT</em> treat responses to such URIs as fresh unless the server provides an explicit expiration time. This specifically means that 1150 1150 responses from HTTP/1.0 servers for such URIs <em class="bcp14">SHOULD NOT</em> be taken from a cache. See <a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 8.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> for related information. 1151 1151 </p> … … 1865 1865 <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a> Since draft-ietf-httpbis-p6-cache-01 1866 1866 </h2> 1867 <p id="rfc.section.B.3.p.1">Closed issues: </p> 1868 <ul> 1869 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82</a>>: "rel_path not used" 1870 </li> 1871 </ul> 1867 1872 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 1868 1873 <p>Copyright © The IETF Trust (2008).</p> -
draft-ietf-httpbis/latest/p6-cache.xml
r172 r173 1375 1375 <t> 1376 1376 We note one exception to this rule: since some applications have 1377 traditionally used GET s and HEADs with query URLs (those containing a1378 "?" in the rel_path part)to perform operations with significant side1377 traditionally used GET and HEAD requests with URLs containing a query part 1378 to perform operations with significant side 1379 1379 effects, caches &MUST-NOT; treat responses to such URIs as fresh unless 1380 1380 the server provides an explicit expiration time. This specifically … … 2909 2909 <section title="Since draft-ietf-httpbis-p6-cache-01"> 2910 2910 <t> 2911 Closed issues: 2912 <list style="symbols"> 2913 <t> 2914 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82"/>: 2915 "rel_path not used" 2916 </t> 2917 </list> 2911 2918 </t> 2912 2919 </section>
Note: See TracChangeset
for help on using the changeset viewer.