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/p1-messaging.xml

    r2398 r2400  
    758758   the server incorrectly implements the HTTP specification, but only
    759759   after the client has attempted at least one normal request and determined
    760    from the response status or header fields (e.g., <x:ref>Server</x:ref>) that
     760   from the response status code or header fields (e.g., <x:ref>Server</x:ref>) that
    761761   the server improperly handles higher request versions.
    762762</t>
     
    11241124</artwork></figure>
    11251125<t>
    1126    The methods defined by this specification can be found in
     1126   The request methods defined by this specification can be found in
    11271127   &methods;, along with information regarding the HTTP method registry
    11281128   and considerations for defining new methods.
     
    51215121  The segment + query components of RFC 3986 have been used to define the
    51225122  request-target, instead of abs_path from RFC 1808.
    5123   The asterisk-form of the request-target is only allowed in the OPTIONS
     5123  The asterisk-form of the request-target is only allowed with the OPTIONS
    51245124  method.
    51255125  (<xref target="request-target"/>)
Note: See TracChangeset for help on using the changeset viewer.