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
URI
Click on the red underlined text to get to the source
... request. It builds on the discipline of reference provided by the
Uniform Resource Identifier (URI) [3][20], as a location (URL ...
... network data object or service that can be identified by a URI,
as defined in section 3.2. Resources may be available in multiple
representations (e.g. multiple languages ...
... client sends a
request to the server in the form of a request method, URI, and
protocol version, followed by a MIME ...
... forwarding agent, receiving requests for a URI in its absolute form,
rewriting all or part of the message, and forwarding the reformatted
request toward the server identified by the URI ...
... URI in its absolute form,
rewriting all or part of the message, and forwarding the reformatted
request toward the server identified by the URI. A gateway is a
receiving agent ...
... URIs in HTTP can be represented in absolute form or relative to some
known base URI, depending upon the context of their use. The two
forms are differentiated by the fact that absolute URIs ...
... base URI, depending upon the context of their use. The two
forms are differentiated by the fact that absolute URIs always begin
with a scheme name followed by a colon.
...
... with a scheme name followed by a colon.
URI = ( absoluteURI | relativeURI ) [ "#" fragment ]
...
... The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs ...
... HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if they
...
... URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if they
provide GET-based forms that could generate such URIs. A server
...
... serve, and SHOULD be able to handle URIs of unbounded length if they
provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI ...
... provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).
...
... URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).
...
... than the server can handle (see section 10.4.15).
Note: Servers should be cautious about depending on URI lengths
above 255 bytes, because some older client ...
... TCP connections on that port of that host, and the Request-URI
for the resource is abs_path. The use of IP addresses in URL ...
... not present in the URL, it MUST be given as "/" when used as a
Request-URI for a resource (section 5.1.2).
...
... URI Comparison ...
...
When comparing two URIs to decide if they match or not, a client
SHOULD use a case-sensitive octet-by-octet comparison ...
... SHOULD use a case-sensitive octet-by-octet comparison of the entire
URIs, with these exceptions:
o A port ...
... port that is empty or not given is equivalent to the default
port for that URI;
o Comparisons of host names ...
... encodings.
For example, the following three URIs are equivalent:
http://abc.com:80/~smith/home.html
...
... entity tag value may
be used for entities obtained by requests on different URIs without
implying anything about the equivalence of those entities.
...
... method token, followed by the
Request-URI and the protocol version, and ending with CRLF. The
...
... token indicates the method to be performed on the resource
identified by the Request-URI. The method is case-sensitive.
...
... Request-URI ...
...
The Request-URI is a Uniform Resource Identifier (section 3.2) and
identifies the resource upon which to apply the request.
...
... identifies the resource upon which to apply the request.
Request-URI = "*" | absoluteURI | abs_path
The three options for Request-URI ...
... Request-URI = "*" | absoluteURI | abs_path
The three options for Request-URI are dependent on the nature of the
request. The asterisk "*" means that the request does not apply to a
particular resource, but to the server itself, and is only allowed
...
... proxies.
The most common form of Request-URI is that used to identify a
resource on an origin server or gateway. In this case the absolute
...
... resource on an origin server or gateway. In this case the absolute
path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
the Request-URI, and the network ...
... path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
the Request-URI, and the network location of the URI (net_loc) MUST
...
... the Request-URI, and the network location of the URI (net_loc) MUST
be transmitted in a Host header field ...
...
followed by the remainder of the Request. Note that the absolute path
cannot be empty; if none is present in the original URI, it MUST be
given as "/" (the server root).
...
...
If a 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
request with "*" as the final Request-URI. For example, the request
OPTIONS http://www.ics.uci.edu:8001 HTTP/1.1 ...
... host "www.ics.uci.edu".
The Request-URI is transmitted in the format specified in section
3.2.1. The origin server MUST decode the Request-URI in order to
...
... The Request-URI is transmitted in the format specified in section
3.2.1. The origin server MUST decode the Request-URI in order to
properly interpret the request. Servers SHOULD respond to invalid
Request-URIs ...
... Request-URI in order to
properly interpret the request. Servers SHOULD respond to invalid
Request-URIs with an appropriate status code.
...
... In requests that they forward, proxies MUST NOT rewrite the
"abs_path" part of a Request-URI in any way except as noted above to
replace a null abs_path with "*", no matter what the proxy does in
...
... identified by an Internet request is determined by examining both the
Request-URI and the Host header field.
...
... Request-URI is an absoluteURI, the host is part of the
Request-URI. Any Host header field value in the request MUST be
...
... ignored.
2. If the Request-URI is not an absoluteURI, and the request
includes a Host header field ...
... header field MAY
attempt to use heuristics (e.g., examination of the URI path for
something unique to a particular host) in order to determine what
...
... | "413" ; Request Entity Too Large
| "414" ; Request-URI Too Large
| "415" ; Unsupported Media Type
...
... Line. These header fields give information about the server and about
further access to the resource identified by the Request-URI.
response-header ...
... communication options available on the request/response chain
identified by the Request-URI. This method allows the client to
...
... method are not cachable.
If the Request-URI is an asterisk ("*"), the OPTIONS request is
intended to apply to the server as a whole. A 200 response SHOULD
include any header fields ...
... proxy by specifying the
destination server in the Request-URI without any path information.
If the Request-URI ...
... Request-URI without any path information.
If the Request-URI is not an asterisk, the OPTIONS request applies
only to the options that are available when communicating with that
resource. A 200 response SHOULD include any header fields ...
... GET method means retrieve whatever information (in the form of an
entity) is identified by the Request-URI. If the Request-URI refers
to a data-producing process, it is the produced data which shall be
...
... entity) is identified by the Request-URI. If the Request-URI refers
to a data-producing process, it is the produced data which shall be
returned as the entity ...
... the entity enclosed in the request as a new subordinate of the
resource identified by the Request-URI in the Request-Line. POST is
designed to allow a uniform method to cover the following functions:
...
... The actual function performed by the POST method is determined by the
server and is usually dependent on the Request-URI. The posted entity
is subordinate to that URI ...
... Request-URI. The posted entity
is subordinate to that URI in the same way that a file is subordinate
to a directory containing it, a news article is subordinate to a
newsgroup ...
... 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
(OK) or 204 (No Content) is the appropriate response status,
depending on whether or not the response includes an entity ...
... method requests that the enclosed entity be stored under the
supplied Request-URI. If the Request-URI refers to an already
existing resource, the enclosed entity ...
... entity be stored under the
supplied Request-URI. If the Request-URI refers to an already
existing resource, the enclosed entity SHOULD be considered as a
...
... modified version of the one residing on the origin server. If the
Request-URI does not point to an existing resource, and that URI is
capable of being defined as a new resource by the requesting user
agent ...
... version of the one residing on the origin server. If the
Request-URI does not point to an existing resource, and that URI is
capable of being defined as a new resource by the requesting user
agent, the origin server can create ...
... capable of being defined as a new resource by the requesting user
agent, the origin server can create the resource with that URI. If a
new resource is created, the origin server MUST inform the user agent ...
... to indicate successful completion of the request. If the resource
could not be created or modified with the Request-URI, an appropriate
error response SHOULD be given that reflects the nature of the
...
...
If the request passes through a cache and the Request-URI identifies
one or more currently cached entities, those entries should be
treated as stale. Responses to this method ...
...
The fundamental difference between the POST and PUT requests is
reflected in the different meaning of the Request-URI. The URI in a
POST request identifies the resource that will handle the enclosed
...
... The fundamental difference between the POST and PUT requests is
reflected in the different meaning of the Request-URI. The URI in a
POST request identifies the resource that will handle the enclosed
entity ...
... some other protocol, or a separate entity that accepts annotations.
In contrast, the URI in a PUT request identifies the entity enclosed
with the request -- the user agent ...
... entity enclosed
with the request -- the user agent knows what URI is intended and the
server MUST NOT attempt to apply the request to some other resource.
If the server desires that the request be applied to a different URI ...
... URI is intended and the
server MUST NOT attempt to apply the request to some other resource.
If the server desires that the request be applied to a different URI,
it MUST send a 301 (Moved Permanently) response; the user agent MAY
...
... request.
A single resource MAY be identified by many different URIs. For
example, an article may have a URI for identifying "the current
version ...
... A single resource MAY be identified by many different URIs. For
example, an article may have a URI for identifying "the current
version" which is separate from the URI identifying each particular
...
... example, an article may have a URI for identifying "the current
version" which is separate from the URI identifying each particular
version. In this case, a PUT request on a general URI ...
... URI identifying each particular
version. In this case, a PUT request on a general URI may result in
several other URIs being defined by the origin server.
...
... version. In this case, a PUT request on a general URI may result in
several other URIs being defined by the origin server.
HTTP/1.1 ...
... method requests that the origin server 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 ...
...
If the request passes through a cache and the Request-URI identifies
one or more currently cached entities, those entries should be
treated as stale. Responses to this method ...
... created. The newly created resource can be referenced by the URI(s)
returned in the entity of the response, with the most specific URL ...
...
The requested resource has been assigned a new permanent URI and any
future references to this resource SHOULD be done using one of the
returned URIs ...
... URI and any
future references to this resource SHOULD be done using one of the
returned URIs. Clients with link editing capabilities SHOULD
...
... link editing capabilities SHOULD
automatically re-link references to the Request-URI to one or more of
the new references returned by the server, where possible. This
...
... response is cachable unless indicated otherwise.
If the new URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method ...
... entity
of the response SHOULD contain a short hypertext note with a
hyperlink to the new URI(s).
If the 301 status code ...
...
The requested resource resides temporarily under a different URI.
Since the redirection may be altered on occasion, the client SHOULD
...
... Since the redirection may be altered on occasion, the client SHOULD
continue to use the Request-URI for future requests. This response is
only cachable if indicated by a Cache-Control or Expires header
field ...
... header
field.
If the new URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method ...
... entity
of the response SHOULD contain a short hypertext note with a
hyperlink to the new URI(s).
If the 302 status code ...
...
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
redirect the user agent to a selected resource. The new URI is not a
substitute reference for the originally requested resource. The 303
response is not cachable, but the response to the second (redirected)
...
... request MAY be cachable.
If the new URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method ...
... entity
of the response SHOULD contain a short hypertext note with a
hyperlink to the new URI(s).
...
...
The server has not found anything matching the Request-URI. No
indication is given of whether the condition is temporary or
permanent.
...
... The method specified in the Request-Line is not allowed for the
resource identified by the Request-URI. The response MUST include an
Allow header containing a list of valid ...
... link editing capabilities SHOULD delete
references to the Request-URI after user approval. If the server does
not know, or has no facility to determine, whether or not the
condition is permanent, the status code ...
... Request-URI Too Long ...
...
The server is refusing to service the request because the Request-URI
is longer than the server is willing to interpret. This rare
condition is only likely to occur when a client ...
... security holes present in some servers using fixed-length
buffers for reading or manipulating the Request-URI.
...
... validate the
user-ID and password for the protection space of the Request-URI.
There are no optional authentication parameters.
...
... authentication parameters.
Upon receipt of an unauthorized request for a URI within the
protection space, the server MAY respond with a challenge like the
following:
...
... where "WallyWorld" is the string assigned by the server to identify
the protection space of the Request-URI.
To receive authorization ...
... as described in appendix 19.6.2.1) or entity-body of the initial
response, with each representation identified by its own URI.
Selection from among the representations may be performed
automatically (if the user agent ...
... header field from all its cache entries for the Request-
URI. This conveys to the server the set of entities currently held by
the cache, so that if any one of these entities matches the requested
...
... field matches that of an existing cache entry for the same Request-
URI, whose entity-tag differs from that of the existing entry, and
...
... the server provides an explicit expiration time. This specifically
means that responses from HTTP/1.0 servers for such URIs should not
be taken from a cache. See section 9.1.1 for related information.
...
... entity. This is either the entity
referred to by the Request-URI, or by the Location or Content-
Location response-headers (if present). These methods ...
... In order to prevent denial of service attacks, an invalidation based
on the URI in a Location or Content-Location header MUST only be
...
... header field lists the set of methods supported by
the resource identified by the Request-URI. The purpose of this field
is strictly to inform the recipient of valid methods ...
... Content-Base entity-header field may be used to specify the base
URI for resolving relative URLs within the entity. This header field ...
...
If no Content-Base field is present, the base URI of an entity is
defined either by its Content-Location ...
... defined either by its Content-Location (if that Content-Location URI
is an absolute URI) or the URI ...
... URI
is an absolute URI) or the URI used to initiate the request, in that
order of precedence. Note, however, that the base URI ...
... URI used to initiate the request, in that
order of precedence. Note, however, that the base URI of the contents
within the entity-body may be redefined within that entity ...
... Content-Encoding is a characteristic of the entity identified by
the Request-URI. Typically, the entity-body is stored with this
encoding ...
... The Content-Location value is not a replacement for the original
requested URI; it is only a statement of the location of the resource
corresponding to this particular entity at the time of the request.
...
... entity at the time of the request.
Future requests MAY use the Content-Location URI if the desire is to
identify the source of that particular entity.
...
... entity with a Content-Location
different from the URI used to retrieve it can be used to respond to
later requests on that Content-Location URI ...
... URI used to retrieve it can be used to respond to
later requests on that Content-Location URI. However, the Content-
Location can be used to differentiate between multiple entities
...
...
If the Content-Location is a relative URI, the URI is interpreted
relative to any Content-Base ...
... If the Content-Location is a relative URI, the URI is interpreted
relative to any Content-Base URI ...
... URI is interpreted
relative to any Content-Base URI provided in the response. If no
Content-Base is provided, the relative URI ...
... URI provided in the response. If no
Content-Base is provided, the relative URI is interpreted relative to
the Request-URI.
...
... The Location response-header field is used to redirect the recipient
to a location other than the Request-URI for completion of the
request or identification of a new resource. For 201 (Created)
...
... methods listed may or may not be applicable to the
Request-URI; the Allow header field (section 14.7) MAY be used to
indicate methods ...
... header field (section 14.7) MAY be used to
indicate methods allowed for a particular URI.
Public = "Public" ":" 1#method ...
... client to specify,
for the server's benefit, the address (URI) of the resource from
which the Request-URI was obtained (the "referrer", although the
...
... address (URI) of the resource from
which the Request-URI was obtained (the "referrer", although the
header field is misspelled.) The Referer request-header ...
... links to be traced for maintenance. The Referer field MUST NOT be
sent if the Request-URI was obtained from a source that does not have
its own URI, such as input from the user keyboard.
...
... sent if the Request-URI was obtained from a source that does not have
its own URI, such as input from the user keyboard.
Referer = "Referer" ":" ( absoluteURI | relativeURI )
...
... Referer: http://www.w3.org/hypertext/DataSources/Overview.html
If the field value is a partial URI, it SHOULD be interpreted
relative to the Request-URI. The URI ...
... If the field value is a partial URI, it SHOULD be interpreted
relative to the Request-URI. The URI MUST NOT include a fragment.
...
... URI, it SHOULD be interpreted
relative to the Request-URI. The URI MUST NOT include a fragment.
...
...
When the cache receives a subsequent request whose Request-URI
specifies one or more cache entries including a Vary header ...
... least one challenge that indicates the authentication scheme(s) and
parameters applicable to the Request-URI.
WWW-Authenticate ...
... the Referer. Even when the personal information has been removed, the
Referer field may indicate a private document's URI whose publication
would be inappropriate.
...
... HTTP server translates
HTTP URIs directly into file system calls, the server MUST take
special care not to serve files that were not intended to be
...
... operating systems use ".." as a path component to indicate a
directory level above the current one. On such a system, an HTTP
server MUST disallow any such construct in the Request-URI if it
would otherwise allow access to a resource outside those intended to
be accessible via the HTTP server ...
... request-header (section 14.23) is
missing from an HTTP/1.1 request, and accept absolute URIs (section
5.1.2) are among the most important changes defined by this
specification.
...
... request-header.
o Servers MUST accept absolute URIs.
...
... list of differences between the original version of the resource
identified by the Request-URI and the desired content of the resource
after the PATCH action has been applied. The list of differences is
in a format defined by the media type ...
...
If the request passes through a cache and the Request-URI identifies
a currently cached entity, that entity ...
... method establishes one or more Link relationships between
the existing resource identified by the Request-URI and other
existing resources. The difference between LINK and other methods ...
...
If the request passes through a cache and the Request-URI identifies
a currently cached entity, that entity ...
... removes one or more Link relationships from the
existing resource identified by the Request-URI. These relationships
may have been established using the LINK method ...
...
If the request passes through a cache and the Request-URI identifies
a currently cached entity, that entity ...
... The Derived-From field is required for PUT and PATCH requests if the
entity being sent was previously retrieved from the same URI and a
Content-Version header ...
... URI ...
...
field (above). Its primary purpose has been to include a list of
additional URIs for the resource, including names and mirror
locations. However, it has become clear that the combination of many
different functions within this single field has been a barrier to
...
... Link header field. The
URI header field is therefore deprecated in favor of those other
fields.
...