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
URL
Click on the red underlined text to get to the source
... Universal Resource Identifiers , and finally the
combination of Uniform Resource Locators (URL) and Names (URN). As
far as HTTP ...
... reserved, extra, safe, and unsafe>
For definitive information on URL syntax and semantics, see RFC 1738(-> 4266prop | 4248prop)
...
... BNF above includes national characters not
allowed in valid URLs as specified by RFC 1738(-> 4266prop | 4248prop), since HTTP servers
...
... http URL ...
... HTTP
protocol. This section defines the scheme-specific syntax and
semantics for http URLs.
http_URL ...
... Request-URI
for the resource is abs_path. The use of IP addresses in URL's SHOULD
be avoided whenever possible (see RFC 1900 [24 ...
... 1900 [24]). If the abs_path is
not present in the URL, it MUST be given as "/" when used as a
Request-URI for a resource (section 5.1.2).
...
... header
field (section 14.15) SHOULD be included in the body-part of each
enclosed entity that can be identified by a URL.
In general, an HTTP ...
... proxy from changing the
meaning of the request when the origin server is improperly using a
non-reserved URL character for a reserved purpose. Implementers
should be aware that some pre-HTTP/1.1 ...
... recipient MAY attempt to guess the media type via inspection of its
content and/or the name extension(s) of the URL used to identify the
resource. If the media type remains unknown, the recipient SHOULD
...
... connections, a separate TCP connection was
established to fetch each URL, increasing the load on HTTP servers
and causing congestion ...
... URI(s)
returned in the entity of the response, with the most specific URL
for the resource given by a Location header field. The origin server
...
...
If the server has a preferred choice of representation, it SHOULD
include the specific URL for that representation in the Location
field; user agents MAY use the Location field value for automatic
...
...
If the new URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method was HEAD, the entity ...
...
If the new URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method was HEAD, the entity ...
...
If the new URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method was HEAD, the entity ...
... The requested resource MUST be accessed through the proxy given by
the Location field. The Location field gives the URL of the proxy.
The recipient is expected to repeat the request via the proxy ...
... query
information, when the client has descended into a URL "black hole" of
redirection (e.g., a redirected URL ...
... (case-sensitive), in combination with the canonical root URL (see
section 5.1.2) of the server being accessed, defines the protection
space. These realms allow the protected resources on a server to be
...
... We note one exception to this rule: since some applications have
traditionally used GETs and HEADs with query URLs (those containing a
"?" in the rel_path part) to perform operations with significant side
effects, caches ...
... "?" in the rel_path part) to perform operations with significant side
effects, caches MUST NOT treat responses to such URLs as fresh unless
the server provides an explicit expiration time. This specifically
means that responses from HTTP/1.0 ...
... considerations may force service authors to resort to other means
of preventing caching (e.g. "once-only" URLs) in order not to
suffer the effects of improperly functioning history mechanisms.
...
... entity-header field may be used to specify the base
URI for resolving relative URLs within the entity. This header field
...
... Content-Base header field is present, the value of Content-
Location also defines the base URL for the entity (see section
14.11).
...
... host and port
number of the resource being requested, as obtained from the original
URL given by the user or referring resource (generally an HTTP URL ...
... URL given by the user or referring resource (generally an HTTP URL,
as described in section 3.2.2). The Host field value MUST represent
...
... network location of the origin server or gateway given by the
original URL. This allows the origin server or gateway to
differentiate between internally-ambiguous URLs ...
... URL. This allows the origin server or gateway to
differentiate between internally-ambiguous URLs, such as the root "/"
URL ...
... port for the service requested (e.g., "80" for an HTTP URL). For
example, a request on the origin server for
<http://www.w3.org/pub/WWW/> MUST include:
...
... request
messages on the Internet (i.e., on any message corresponding to a
request for a URL which includes an Internet host address ...
... created
by the request. For 3xx responses, the location SHOULD indicate the
server's preferred URL for automatic redirection to the resource. The
field value consists of a single absolute URL.
...
... server's preferred URL for automatic redirection to the resource. The
field value consists of a single absolute URL.
Location = "Location" ":" absoluteURI
...
... Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738(-> 4266prop | 4248prop), CERN, Xerox PARC, University of Minnesota, December 1994. ...
... Joe Touch, John Heidemann, and Katia Obraczka, "Analysis of HTTP Performance", <URL: http://www.isi.edu/lsam/ib/http-perf/>, USC/Information Sciences Institute, June 1996 ...
... Spero, S., "Analysis of HTTP Performance Problems" <URL:http://sunsite.unc.edu/mdma-release/http-prob.html>. ...
... domain
names to be used in root-level HTTP URLs. Given the rate of growth of
the Web, and the number of servers already deployed, it is extremely
important that all implementations of HTTP ...