Changeset 465 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 03/03/09 13:03:21 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r460 r465 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">March 1, 2009</td>473 <td class="header right">March 3, 2009</td> 474 474 </tr> 475 475 </table> … … 1378 1378 </dl> 1379 1379 <p id="rfc.section.5.1.2.p.18">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 1380 would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-targetToo Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1380 would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1381 1381 </p> 1382 1382 <p id="rfc.section.5.1.2.p.19">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.
Note: See TracChangeset
for help on using the changeset viewer.