Changeset 392
- Timestamp:
- 15/11/08 01:00:30 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r391 r392 1346 1346 </dl> 1347 1347 <p id="rfc.section.5.1.2.p.15">HTTP does not place a pre-defined limit on the length of a request-target. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (URI too long) status if the received request-target 1348 would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request- URIToo Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1348 would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-target Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1349 1349 </p> 1350 1350 <p id="rfc.section.5.1.2.p.16">Various ad-hoc limitations on request-target length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support request-target lengths of 8000 or more OCTETs. … … 2754 2754 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/134">http://tools.ietf.org/wg/httpbis/trac/ticket/134</a>>: "RFC822 reference left in discussion of date formats" 2755 2755 </li> 2756 </ul> 2757 <p id="rfc.section.D.7.p.2">Other changes: </p> 2758 <ul> 2759 <li>Rewrite introduction; add mostly new Architecture Section.</li> 2756 2760 </ul> 2757 2761 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
Note: See TracChangeset
for help on using the changeset viewer.