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
service
Click on the red underlined text to get to the source
... A network data object or service that can be identified by a URI,
as defined in section 3.2. Resources may be available in multiple
...
... An application program that accepts connections in order to
service requests by sending back responses. Any given program may
be capable of being both a client and a server; our use of these
...
... binary data over a 7-bit transport service. However, safe transport
has a different focus for an 8bit ...
... links to that resource be removed. Such an event is common for
limited-time, promotional services and for resources belonging to
individuals no longer working at the server's site. It is not
necessary to mark all permanently unavailable ...
...
The server is refusing to service the request because the Request-URI
is longer than the server is willing to interpret. This rare
...
...
The server is refusing to service the request because the entity of
the request is in a format not supported by the requested resource
...
... Service Unavailable ...
... opaque string which
can only be compared for equality with other realms on that server.
The server will service the request only if it can validate the
user-ID and password ...
... The principle behind entity tags is that only the service author
knows the semantics of a resource well enough to select an
...
... may be because absolute semantic transparency is deemed necessary by
the service author, or because of security or privacy considerations.
...
... o POST
In order to prevent denial of service attacks, an invalidation based
on the URI in a Location or Content-Location ...
...
Note: if history list mechanisms unnecessarily prevent users from
viewing stale resources, this will tend to force service authors to
avoid using HTTP expiration controls and cache ...
... HTTP expiration controls and cache controls when they
would otherwise like to. Service authors may consider it important
that users not be presented with error messages or warning messages
...
... to cached, or ought to expire quickly, user interface
considerations may force service authors to resort to other means
of preventing caching (e.g. "once-only" URLs) in order not to
...
... The purpose of this directive is to meet the stated requirements of
certain users and service authors who are concerned about accidental
releases of information via unanticipated accesses to cache data
structures ...
... authenticated once by that user), while still requiring proxies that
service many users to revalidate each time (in order to make sure
that each user has been authenticated). Note that such authenticated ...
... port information implies the default
port for the service requested (e.g., "80" for an HTTP URL). For
...
... host address for the
service being requested). If the Host field is not already present,
an HTTP/1.1 ...
... The Retry-After response-header field can be used with a 503 (Service
Unavailable) response to indicate how long the service ...
... Service
Unavailable) response to indicate how long the service is expected to
be unavailable to the requesting client ...
... header fields
generated by the server, that such sending could improve the quality
of service.
Elaborate user-customized accept header fields ...
... Clients using HTTP rely heavily on the Domain Name Service, and are
thus generally prone to security attacks based on the deliberate
...