1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
method
Click on the red underlined text to get to the source
... HTTP
allows an open-ended set of methods that indicate the purpose of a
request. It builds on the discipline of reference provided by the
Uniform Resource Identifier ...
... 4] or
name (URN) , for indicating the resource to which a method is to be
applied. Messages are passed in a format similar to that used by
Internet mail ...
... request/response protocol. A client sends a
request to the server in the form of a request method, URI, and
protocol version ...
... The term "character set" is used in this document to refer to a
method used with one or more tables to convert a sequence of octets
into a sequence of characters. Note that unconditional conversion
...
... character encodings, from simple single-table mappings such as US-
ASCII to complex table switching methods such as those that use ISO
2022's techniques. However, the definition associated with a MIME ...
... Note: The "multipart/form-data" type has been specifically defined
for carrying form data suitable for processing via the POST request
method, as described in RFC 1867hist(-> 2854) [15].
...
... message-headers. A message-body MAY be included in a
request only when the request method (section 5.1.1) allows an
entity-body.
...
... For response messages, whether or not a message-body is included with
a message is dependent on both the request method and the response
status code (section 6.1.1). All responses to the HEAD request ...
... status code (section 6.1.1). All responses to the HEAD request method
MUST NOT include a message-body, even though the presence of entity ...
... request message from a client to a server includes, within the
first line of that message, the method to be applied to the resource,
the identifier of the resource, and the protocol version ...
... Method ...
... The Method token indicates the method to be performed on the resource
identified by the Request-URI. The method ...
... method to be performed on the resource
identified by the Request-URI. The method is case-sensitive.
Method ...
... method is case-sensitive.
Method = "OPTIONS" ; Section 9.2
| "GET" ; Section 9.3
| "HEAD" ; Section 9.4
...
... token
The list of methods allowed by a resource can be specified in an
Allow header field (section 14.7). The return code ...
... return code of the response
always notifies the client whether a method is currently allowed on a
resource, since the set of allowed methods can change dynamically.
...
... client whether a method is currently allowed on a
resource, since the set of allowed methods can change dynamically.
Servers SHOULD return the status code 405 (Method ...
... methods can change dynamically.
Servers SHOULD return the status code 405 (Method Not Allowed) if the
method is known by the server ...
... status code 405 (Method Not Allowed) if the
method is known by the server but not allowed for the requested
resource, and 501 (Not Implemented) if the method ...
... method is known by the server but not allowed for the requested
resource, and 501 (Not Implemented) if the method is unrecognized or
not implemented by the server. The list of methods ...
... method is unrecognized or
not implemented by the server. The list of methods known by a server
can be listed in a Public response-header field (section 14.35).
...
... header field (section 14.35).
The methods GET and HEAD MUST be supported by all general-purpose
servers. All other methods are optional; however, if the above
...
... The methods GET and HEAD MUST be supported by all general-purpose
servers. All other methods are optional; however, if the above
methods are implemented, they MUST be implemented with the same
...
... servers. All other methods are optional; however, if the above
methods are implemented, they MUST be implemented with the same
semantics as those specified in section 9.
...
... request. The asterisk "*" means that the request does not apply to a
particular resource, but to the server itself, and is only allowed
when the method used does not necessarily apply to a resource. One
example would be
...
... proxy receives a request without any path in the Request-URI and
the method specified is capable of supporting the asterisk form of
request, then the last proxy on the request chain MUST forward the
...
... | "403" ; Forbidden
| "404" ; Not Found
| "405" ; Method Not Allowed
| "406" ; Not Acceptable
| "407" ; Proxy ...
... Request and Response messages MAY transfer an entity if not otherwise
restricted by the request method or response status code. An entity
...
... transport connection and retransmit the aborted request without user
interaction so long as the request method is idempotent (see section
9.1.2); other methods ...
... method is idempotent (see section
9.1.2); other methods MUST NOT be automatically retried, although
user agents MAY offer a human operator the choice of retrying the
...
... connection or it MAY
continue to read and discard the rest of the request. It MUST NOT
perform the requested method if it returns an error status.
...
... receiving any status from the server, the client SHOULD retry
the request without user interaction so long as the request method is
idempotent (see section 9.1.2); other methods MUST NOT be
...
... the request without user interaction so long as the request method is
idempotent (see section 9.1.2); other methods MUST NOT be
automatically retried, although user agents MAY offer a human
...
... Method Definitions ...
...
The set of common methods for HTTP/1.1 is defined below. Although
this set can be expanded, additional methods ...
... methods for HTTP/1.1 is defined below. Although
this set can be expanded, additional methods cannot be assumed to
share the same semantics for separately extended clients and servers ...
... Safe and Idempotent Methods ...
... Safe Methods ...
...
In particular, the convention has been established that the GET and
HEAD methods should never have the significance of taking an action
other than retrieval. These methods should be considered "safe." This
...
... HEAD methods should never have the significance of taking an action
other than retrieval. These methods should be considered "safe." This
allows user agents to represent other methods ...
... methods should be considered "safe." This
allows user agents to represent other methods, such as POST, PUT and
DELETE, in a special way, so that the user is made aware of the fact
...
... Idempotent Methods ...
...
Methods may also have the property of "idempotence" in that (aside
from error or expiration issues) the side-effects of N > 0 identical
...
... from error or expiration issues) the side-effects of N > 0 identical
requests is the same as for a single request. The methods GET, HEAD,
PUT and DELETE share this property.
...
...
The OPTIONS method represents a request for information about the
communication options available on the request/response chain
...
... request/response chain
identified by the Request-URI. This method allows the client to
determine the options and/or requirements ...
... communication options (e.g., Allow is appropriate, but Content-Type
is not). Responses to this method are not cachable.
If the Request-URI ...
...
The GET method means retrieve whatever information (in the form of an
entity) is identified by the Request-URI ...
...
The semantics of the GET method change to a "conditional GET" if the
request message includes an If-Modified-Since, If-Unmodified-Since,
...
... If-Match, If-None-Match, or If-Range header field. A conditional GET
method requests that the entity be transferred only under the
circumstances described by the conditional header field ...
... circumstances described by the conditional header field(s). The
conditional GET method is intended to reduce unnecessary network
usage by allowing cached entities to be refreshed without requiring
...
...
The semantics of the GET method change to a "partial GET" if the
request message includes a Range ...
... that only part of the entity be transferred, as described in section
14.36. The partial GET method is intended to reduce unnecessary
network usage by allowing partially-retrieved entities to be
...
...
The HEAD method is identical to GET except that the server MUST NOT
return a message-body in the response. The metainformation contained
...
... HTTP headers in response to a HEAD request SHOULD be identical
to the information sent in response to a GET request. This method can
be used for obtaining metainformation about the entity implied by the
...
... entity implied by the
request without transferring the entity-body itself. This method is
often used for testing hypertext links for validity ...
... resource identified by the Request-URI in the Request-Line. POST is
designed to allow a uniform method to cover the following functions:
o Annotation of existing resources;
...
... database through an append operation.
The actual function performed by the POST method is determined by the
server and is usually dependent on the Request-URI. The posted entity ...
... database.
The action performed by the POST method might not result in a
resource that can be identified by a URI. In this case, either 200
...
... header (see section 14.30).
Responses to this method are not cachable, unless the response
includes appropriate Cache-Control or Expires header fields ...
... Request-URI identifies
one or more currently cached entities, those entries should be
treated as stale. Responses to this method are not cachable.
The fundamental difference between the POST and PUT requests is
...
...
The DELETE method requests that the origin server delete the resource
identified by the Request-URI ...
... delete the resource
identified by the Request-URI. This method MAY be overridden by human
intervention (or other means) on the origin server. The client cannot
...
... Request-URI identifies
one or more currently cached entities, those entries should be
treated as stale. Responses to this method are not cachable.
...
...
The TRACE method is used to invoke a remote, application-layer loop-
back of the request message ...
... entity-body, with a Content-Type of "message/http". Responses
to this method MUST NOT be cached.
...
...
Each Status-Code is described below, including a description of which
method(s) it can follow and any metainformation required in the
response.
...
...
The request has succeeded. The information returned with the response
is dependent on the method used in the request, for example:
GET an entity ...
... by the user agent without interaction
with the user if and only if the method used in the second request is
GET or HEAD. A user agent SHOULD NOT automatically redirect a request
...
... URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method was HEAD, the entity
of the response SHOULD contain a short hypertext note with a
...
... URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method was HEAD, the entity
of the response SHOULD contain a short hypertext note with a
...
... The response to the request can be found under a different URI and
SHOULD be retrieved using a GET method on that resource. This method
exists primarily to allow the output of a POST-activated script to
...
... URI and
SHOULD be retrieved using a GET method on that resource. This method
exists primarily to allow the output of a POST-activated script to
redirect the user agent ...
... URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method was HEAD, the entity
of the response SHOULD contain a short hypertext note with a
...
... error situation, and whether it is a temporary or permanent
condition. These status codes are applicable to any request method.
User agents SHOULD display any included entity ...
... Authorization will not help and the request SHOULD NOT be repeated.
If the request method was not HEAD and the server wishes to make
public why the request has not been fulfilled, it SHOULD describe the
reason for the refusal in the entity ...
... Method Not Allowed ...
...
The method specified in the Request-Line is not allowed for the
resource identified by the Request-URI. The response MUST include an
...
... metainformation (header field data) and thus prevent the requested
method from being applied to a resource other than the one intended.
...
... entity of
the request is in a format not supported by the requested resource
for the requested method.
...
... The server does not support the functionality required to fulfill the
request. This is the appropriate response when the server does not
recognize the request method and is not capable of supporting it for
any resource.
...
... negotiation are orthogonal and thus may be used separately or in
combination. One method of combination, referred to as transparent
negotiation, occurs when a cache ...
... interact with each other, it is useful to describe the basic caching
design of HTTP separately from the detailed descriptions of methods,
headers, response codes ...
... entry is invalid, the HTTP/1.1 protocol supports the use of
conditional methods.
The key protocol features for supporting conditional methods ...
... methods.
The key protocol features for supporting conditional methods are
those concerned with "cache validators." When an origin server
...
... header (which includes the validator) that implicitly turns the
method (usually, GET) into a conditional.
The protocol includes both positive and negative senses of cache ...
... cache-
validating conditions. That is, it is possible to request either that
a method be performed if and only if a validator matches or if and
only if no validators match.
...
... Date value.
This method relies on the fact that if two different responses were
sent by the origin server during the same second, but both had the
same Last-Modified time, then at least one of those responses would
...
...
Unless the origin server explicitly prohibits the caching of their
responses, the application of GET and HEAD methods to any resources
SHOULD NOT have side effects that would lead to erroneous behavior if
these responses are taken from a cache ...
...
The effect of certain methods at the origin server may cause one or
more existing cache entries to become non-transparently invalid. That
...
... Request-URI, or by the Location or Content-
Location response-headers (if present). These methods are:
o PUT
...
...
All methods that may be expected to cause modifications to the origin
server's resources MUST be written through to the origin server. This
currently includes all methods ...
... methods that may be expected to cause modifications to the origin
server's resources MUST be written through to the origin server. This
currently includes all methods except for GET and HEAD. A cache MUST
NOT reply to such a request from a client ...
... The Allow entity-header field lists the set of methods supported by
the resource identified by the Request-URI. The purpose of this field
...
... Request-URI. The purpose of this field
is strictly to inform the recipient of valid methods associated with
the resource. An Allow header field MUST be present in a 405 (Method ...
... methods associated with
the resource. An Allow header field MUST be present in a 405 (Method
Not Allowed) response.
...
... Not Allowed) response.
Allow = "Allow" ":" 1#method
Example of use:
...
...
This field cannot prevent a client from trying other methods.
However, the indications given by the Allow header field value SHOULD
...
... However, the indications given by the Allow header field value SHOULD
be followed. The actual set of allowed methods is defined by the
origin server at the time of each request.
...
... The Allow header field MAY be provided with a PUT request to
recommend the methods to be supported by the new or modified
resource. The server is not required to support these methods and
...
... recommend the methods to be supported by the new or modified
resource. The server is not required to support these methods and
SHOULD include an Allow header in the response giving the actual
...
... proxy MUST NOT modify the Allow header field even if it does not
understand all the methods specified, since the user agent MAY have
other means of communicating with the origin server.
...
...
The Allow header field does not indicate what methods are implemented
at the server level. Servers MAY use the Public response-header field
...
... at the server level. Servers MAY use the Public response-header field
(section 14.35) to describe what methods are implemented on the
server as a whole.
...
... By default, a response is cachable if the requirements of the request
method, request header fields, and the response status indicate that
it is cachable. Section 13.4 summarizes these defaults for
...
... message-body, in decimal number of octets, sent to the recipient or,
in the case of the HEAD method, the size of the entity-body that
would have been sent had the request been a GET.
...
... media type of the
entity-body sent to the recipient or, in the case of the HEAD method,
the media type that would have been sent had the request been a GET.
...
... be used as an insecure form of access protection. The interpretation
of this field is that the request is being performed on behalf of the
person given, who accepts responsibility for the method performed. In
particular, robot agents SHOULD include this header ...
...
The If-Modified-Since request-header field is used with the GET
method to make it conditional: if the requested variant has not been
modified since the time specified in this field, an entity will not
...
...
The If-Match request-header field is used with a method to make it
conditional. A client that has one or more entities previously
...
... and any current entity exists for that resource, then the server MAY
perform the requested method as if the If-Match header field did not
exist.
...
... tags match, or if "*" is given and no current
entity exists, the server MUST NOT perform the requested method, and
MUST return a 412 (Precondition Failed) response. This behavior is
most useful when the client wants ...
... MUST return a 412 (Precondition Failed) response. This behavior is
most useful when the client wants to prevent an updating method, such
as PUT, from modifying a resource that has changed since the client
...
... ignored.
The meaning of "If-Match: *" is that the method SHOULD be performed
if the representation selected by the origin server (or by a cache,
...
... update a resource (e.g., a PUT) MAY include an
If-Match header field to signal that the request method MUST NOT be
applied if the entity corresponding to the If-Match value (a single
entity ...
...
The If-None-Match request-header field is used with a method to make
it conditional. A client that has one or more entities previously
...
... given and any current entity exists for that resource, then the
server MUST NOT perform the requested method. Instead, if the request
method was GET or HEAD, the server SHOULD respond with a 304 (Not
...
... server MUST NOT perform the requested method. Instead, if the request
method was GET or HEAD, the server SHOULD respond with a 304 (Not
Modified) response, including the cache-related entity ...
... header fields
(particularly ETag) of one of the entities that matched. For all
other request methods, the server MUST respond with a status of 412
(Precondition Failed).
...
... tags match, or if "*" is given and no current
entity exists, then the server MAY perform the requested method as if
the If-None-Match header field did not exist.
...
... MUST be ignored.
The meaning of "If-None-Match: *" is that the method MUST NOT be
performed if the representation selected by the origin server (or by
a cache ...
...
The If-Unmodified-Since request-header field is used with a method to
make it conditional. If the requested resource has not been modified
since the time specified in this field, the server should perform the
...
... request-header field may be used with the TRACE
method (section 14.31) to limit the number of proxies or gateways
...
...
The Max-Forwards header field SHOULD be ignored for all other methods
defined by this specification and for any extension methods for which
...
... header field SHOULD be ignored for all other methods
defined by this specification and for any extension methods for which
it is not explicitly referred to as part of that method definition.
...
... defined by this specification and for any extension methods for which
it is not explicitly referred to as part of that method definition.
...
...
The Public response-header field lists the set of methods supported
by the server. The purpose of this field is strictly to inform the
...
... by the server. The purpose of this field is strictly to inform the
recipient of the capabilities of the server regarding unusual
methods. The methods listed may or may not be applicable to the
...
... recipient of the capabilities of the server regarding unusual
methods. The methods listed may or may not be applicable to the
Request-URI ...
... Request-URI; the Allow header field (section 14.7) MAY be used to
indicate methods allowed for a particular URI.
...
... HTTP retrieval requests using conditional or unconditional GET
methods may request one or more sub-ranges of the entity, instead of
...
... to use a "better" protocol if available (where "better" is determined
by the server, possibly according to the nature of the method and/or
resource being requested).
...
... character set other than ISO-8859-1 is used, it MUST be encoded
in the warn-text using the method described in RFC 1522(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft) [14].
...
...
The Basic authentication scheme is not a secure method of user
authentication, nor does it in any way protect the entity, which is
...
... HTTP cannot regulate the
content of the data that is transferred, nor is there any a priori
method of determining the sensitivity of any particular piece of
information within the context of any given request. Therefore,
...
... Additional Request Methods ...
...
The PATCH method is similar to PUT except that the entity contains a
list of differences between the original version ...
... method are not cachable.
The actual method for determining how the patched resource is placed,
and what happens to its predecessor, is defined entirely by the
origin server. If the original version ...
...
The LINK method establishes one or more Link relationships between
the existing resource identified by the Request-URI ...
... Request-URI and other
existing resources. The difference between LINK and other methods
allowing links ...
... links to be established between resources is that the LINK
method does not allow any message-body to be sent in the request and
does not directly result in the creation of new resources.
...
... Request-URI. These relationships
may have been established using the LINK method or by any other
method supporting the Link ...