Ignore:
Timestamp:
15/09/13 00:57:24 (8 years ago)
Author:
fielding@…
Message:

uniform terminology for status code and request method (except where it is obvious by context)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2397 r2400  
    322322   A response message is considered complete when all of the octets indicated
    323323   by the message framing (&messaging;) are received prior to the connection
    324    being closed. If the request is GET, the response status is <x:ref>200
    325    (OK)</x:ref>, and the entire response header block has been received, a
     324   being closed. If the request method is GET, the response status code is
     325   <x:ref>200 (OK)</x:ref>, and the entire response header block has been received, a
    326326   cache &MAY; store an incomplete response message body if the cache entry is
    327327   recorded as incomplete. Likewise, a <x:ref>206 (Partial Content)</x:ref>
     
    11131113   (&effective-request-uri;) as well as the URI(s) in the
    11141114   <x:ref>Location</x:ref> and <x:ref>Content-Location</x:ref> response header
    1115    fields (if present) when a non-error response to a request with an unsafe
    1116    method is received.
     1115   fields (if present) when a non-error status code is received in response to
     1116   an unsafe request method.
    11171117</t>
    11181118<t>
Note: See TracChangeset for help on using the changeset viewer.