Ignore:
Timestamp:
Mar 29, 2012, 4:28:19 AM (8 years ago)
Author:
julian.reschke@…
Message:

remove redundant ABNF, fix section title

File:
1 edited

Legend:

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

    r1632 r1635  
    3434  <!ENTITY methods                "<xref target='Part2' x:rel='#methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3535  <!ENTITY OPTIONS                "<xref target='Part2' x:rel='#OPTIONS' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    36   <!ENTITY status-code-reasonphr  "<xref target='Part2' x:rel='#status.code.and.reason.phrase' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3736  <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3837  <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    836835   (<xref target="message.routing"/>) to the server.
    837836   If the server responds to that request with a non-interim HTTP response
    838    message, as described in &status-code-reasonphr;, then that response
     837   message, as described in &status-codes;, then that response
    839838   is considered an authoritative answer to the client's request.
    840839</t>
     
    10981097<t anchor="status-code">
    10991098   The status-code element is a 3-digit integer result code of the attempt to
    1100    understand and satisfy the request. See &status-code-reasonphr; for
     1099   understand and satisfy the request. See &status-codes; for
    11011100   further information, such as the list of status codes defined by this
    11021101   specification, the IANA registry, and considerations for new status codes.
Note: See TracChangeset for help on using the changeset viewer.