Changeset 423


Ignore:
Timestamp:
Nov 21, 2008, 7:57:12 AM (11 years ago)
Author:
julian.reschke@…
Message:

make reason phrase for 414 consistent again (related to #34)

Location:
draft-ietf-httpbis/latest
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r421 r423  
    13561356         </dd>
    13571357      </dl>
    1358       <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
    1359          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.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1358      <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 (Request-target too Long) status if the received
     1359         request-target 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.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    13601360      </p>
    13611361      <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.

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r421 r423  
    16051605   HTTP does not place a pre-defined limit on the length of a request-target.
    16061606   A server &MUST; be prepared to receive URIs of unbounded length and
    1607    respond with the 414 (URI too long) status if the received
     1607   respond with the 414 (Request-target too Long) status if the received
    16081608   request-target would be longer than the server wishes to handle
    16091609   (see &status-414;).

  • draft-ietf-httpbis/latest/p2-semantics.html

    r421 r423  
    824824       / "412"  ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;9.4.13</a>: Precondition Failed
    825825       / "413"  ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section&nbsp;9.4.14</a>: Request Entity Too Large
    826        / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-target Too Long">Section&nbsp;9.4.15</a>: Request-target Too Large
     826       / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-target Too Long">Section&nbsp;9.4.15</a>: Request-target Too Long
    827827       / "415"  ; <a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;9.4.16</a>: Unsupported Media Type
    828828       / "416"  ; <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;9.4.17</a>: Requested range not satisfiable

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r421 r423  
    545545       / "412"  ; <xref target="status.412"/>: Precondition Failed
    546546       / "413"  ; <xref target="status.413"/>: Request Entity Too Large
    547        / "414"  ; <xref target="status.414"/>: Request-target Too Large
     547       / "414"  ; <xref target="status.414"/>: Request-target Too Long
    548548       / "415"  ; <xref target="status.415"/>: Unsupported Media Type
    549549       / "416"  ; <xref target="status.416"/>: Requested range not satisfiable
Note: See TracChangeset for help on using the changeset viewer.