Ignore:
Timestamp:
Mar 3, 2009, 5:03:21 AM (11 years ago)
Author:
julian.reschke@…
Message:

Make reason phrase for status 414 consistent again (now: "URI Too Long")

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r460 r465  
    471471         <tr>
    472472            <td class="header left"></td>
    473             <td class="header right">March 1, 2009</td>
     473            <td class="header right">March 3, 2009</td>
    474474         </tr>
    475475      </table>
     
    13781378      </dl>
    13791379      <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-target 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>).
     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>).
    13811381      </p>
    13821382      <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.