Ignore:
Timestamp:
19/01/14 02:53:35 (7 years ago)
Author:
fielding@…
Message:

(editorial) add section xrefs where the common method names are first used; see #531

File:
1 edited

Legend:

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

    r2557 r2561  
    2626  <!ENTITY diff-mime              "<xref target='Part2' x:rel='#differences.between.http.and.mime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2727  <!ENTITY representation         "<xref target='Part2' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     28  <!ENTITY GET                    "<xref target='Part2' x:rel='#GET' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2829  <!ENTITY HEAD                   "<xref target='Part2' x:rel='#HEAD' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2930  <!ENTITY header-allow           "<xref target='Part2' x:rel='#header.allow' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    364365<t>
    365366   The following example illustrates a typical message exchange for a
    366    GET request on the URI "http://www.example.com/hello.txt":
     367   GET request (&GET;) on the URI "http://www.example.com/hello.txt":
    367368</t>
    368369<figure><preamble>
     
    15431544   the request method to which it is responding and the response
    15441545   status code (<xref target="status.line"/>).
    1545    Responses to the HEAD request method never include a message body
     1546   Responses to the HEAD request method (&HEAD;) never include a message body
    15461547   because the associated response header fields (e.g.,
    15471548   <x:ref>Transfer-Encoding</x:ref>, <x:ref>Content-Length</x:ref>, etc.),
    15481549   if present, indicate only what their values would have been if the request
    1549    method had been GET (&HEAD;).
    1550    <x:ref>2xx (Successful)</x:ref> responses to CONNECT switch to tunnel
    1551    mode instead of having a message body (&CONNECT;).
     1550   method had been GET (&GET;).
     1551   <x:ref>2xx (Successful)</x:ref> responses to a CONNECT request method
     1552   (&CONNECT;) switch to tunnel mode instead of having a message body.
    15521553   All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and
    15531554   <x:ref>304 (Not Modified)</x:ref> responses do not include a message body.
Note: See TracChangeset for help on using the changeset viewer.