Ignore:
Timestamp:
15/09/13 01:06:52 (7 years ago)
Author:
fielding@…
Message:

uniform terminology for header section instead of header block; this and [2400] addresses #234

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2400 r2401  
    11311131   <c><xref target="GET" format="counter"/></c>
    11321132   <c>HEAD</c>
    1133    <c>Same as GET, but only transfer the status line and header block.</c>
     1133   <c>Same as GET, but only transfer the status line and header section.</c>
    11341134   <c><xref target="HEAD" format="counter"/></c>
    11351135   <c>POST</c>
     
    13351335   The HEAD method is identical to GET except that the server &MUST-NOT;
    13361336   send a message body in the response (i.e., the response terminates at the
    1337    end of the header block). The server &SHOULD; send the same header fields
     1337   end of the header section). The server &SHOULD; send the same header fields
    13381338   in response to a HEAD request as it would have sent if the request had been
    13391339   a GET, except that the payload header fields (<xref target="payload"/>)
     
    16391639   that the sender (and all inbound proxies) will switch to tunnel mode
    16401640   immediately after the blank line that concludes the successful response's
    1641    header block; data received after that blank line is from the server
     1641   header section; data received after that blank line is from the server
    16421642   identified by the request-target.
    16431643   Any response other than a successful response indicates that the tunnel
     
    27242724   All 1xx responses consist of only the status-line and optional header
    27252725   fields, and thus are terminated by the empty line at the end of the header
    2726    block.
     2726   section.
    27272727   Since HTTP/1.0 did not define any 1xx status codes, servers &MUST-NOT; send
    27282728   a 1xx response to an HTTP/1.0 client except under experimental conditions.
     
    28322832   <x:dfn>204 (No Content)</x:dfn> instead.
    28332833   For CONNECT, no payload is allowed because the successful result is a
    2834    tunnel, which begins immediately after the 200 response header block.
     2834   tunnel, which begins immediately after the 200 response header section.
    28352835</t>
    28362836<t>
     
    38583858   A recipient with a clock that receives a response message without a Date
    38593859   header field &MUST; record the time it was received and append a
    3860    corresponding Date header field to the message's header block if it is
     3860   corresponding Date header field to the message's header section if it is
    38613861   cached or forwarded downstream.
    38623862</t>
Note: See TracChangeset for help on using the changeset viewer.