Ignore:
Timestamp:
03/02/14 05:03:28 (7 years ago)
Author:
fielding@…
Message:

(editorial) fix a very old xref bug, old terminology, and plural issue all in one sentence I have read a million times

File:
1 edited

Legend:

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

    r2614 r2615  
    6161  <!ENTITY status-304             "<xref target='Part4' x:rel='#status.304' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6262  <!ENTITY status-4xx             "<xref target='Part2' x:rel='#status.4xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     63  <!ENTITY status-413             "<xref target='Part2' x:rel='#status.413' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6364  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6465  <!ENTITY iana-header-registry   "<xref target='Part2' x:rel='#header.field.registry' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    39983999</t>
    39994000<t>
    4000    A server can reject messages that
    4001    have request-targets that are too long (&status-414;) or request entities
    4002    that are too large (&status-4xx;). Additional status codes related to
     4001   A server can reject a message that
     4002   has a request-target that is too long (&status-414;) or a request payload
     4003   that is too large (&status-413;). Additional status codes related to
    40034004   capacity limits have been defined by extensions to HTTP
    40044005   <xref target="RFC6585"/>.
Note: See TracChangeset for help on using the changeset viewer.