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
semantic
Click on the red underlined text to get to the source
... messages, containing metainformation about the data transferred and
modifiers on the request/response semantics. However, HTTP/1.0 does
not sufficiently take into consideration the effects of hierarchical
...
... headers can be folded onto multiple lines if the
continuation line begins with a space or horizontal tab. All linear
white space, including folding, has the same semantics as SP.
...
... protocol add features which do not change the general message parsing
algorithm, but which may add to the message semantics and imply
additional capabilities of the sender. The <major> number is
...
...
For definitive information on URL syntax and semantics, see RFC 1738(-> 4266prop | 4248prop)
[4 ...
... network resources via the HTTP
protocol. This section defines the scheme-specific syntax and
semantics for http URLs.
...
... If the port is empty or not given, port 80 is assumed. The semantics
are that the identified resource is located at the server listening
for TCP connections ...
... insensitive. Parameter values may or may not be case-sensitive,
depending on the semantics of the parameter name. Linear white space
(LWS) MUST NOT be used between the type and subtype, nor between an
attribute and its value. User agents ...
... two entities of a resource only if the entities are equivalent and
could be substituted for each other with no significant change in
semantics. A weak entity tag can only be used for weak comparison ...
... header fields into one
"field-name: field-value" pair, without changing the semantics of the
message, by appending each subsequent field-value to the first, each
separated by a comma. The order in which header fields ...
... experimental header fields may be given the semantics of general
header fields if all parties in the communication recognize them to
...
... methods are implemented, they MUST be implemented with the same
semantics as those specified in section 9.
...
... information about the request, and about the client itself, to the
server. These fields act as request modifiers, with semantics
equivalent to the parameters on a programming language ...
... experimental header fields MAY be given the semantics of request-
header fields if all parties in the communication recognize them to
...
... experimental header fields MAY be given the semantics of response-
header fields if all parties in the communication recognize them to
...
... versions of HTTP might optimistically try a new feature, but
if communicating with an older server, retry with old semantics
after an error is reported.
...
... this set can be expanded, additional methods cannot be assumed to
share the same semantics for separately extended clients and servers.
...
... process, unless that text happens to be the output of the process.
The semantics of the GET method change to a "conditional GET" if the
request message ...
... by the client.
The semantics of the GET method change to a "partial GET" if the
request message ...
... database. The realm value
is a string, generally assigned by the origin server, which may have
additional semantics specific to the authentication scheme.
...
... Requirements for performance, availability, and disconnected
operation require us to be able to relax the goal of semantic
transparency. The HTTP/1.1 protocol allows origin servers, caches ...
... elements:
1. Protocol features that provide full semantic transparency when this
is required by all parties.
...
... cache to attach warnings to
responses that do not preserve the requested approximation of
semantic transparency.
A basic principle is that it must be possible for the clients ...
... A basic principle is that it must be possible for the clients to
detect any potential relaxation of semantic transparency.
Note: The server, cache ...
... implementer may be faced with
design decisions not explicitly discussed in this specification. If
a decision may affect semantic transparency, the implementer ought
to err on the side of maintaining transparency unless a careful and
...
... general rule, if there is any apparent conflict between header
values, the most restrictive interpretation should be applied (that
is, the one that is most likely to preserve semantic transparency).
However, in some cases, Cache-Control directives are explicitly
...
... However, in some cases, Cache-Control directives are explicitly
specified as weakening the approximation of semantic transparency
(for example, "max-stale" or "public").
...
... caches, and so cannot
further relax the cache's approximation of semantic transparency.
A client ...
... caches, and so may violate the origin server's specified constraints
on semantic transparency, but may be necessary to support
disconnected operation, or high availability in the face of poor
connectivity.
...
... entity is not
likely to change, in a semantically significant way, before the
expiration time is reached. This normally preserves semantic
transparency, as long as the server's expiration times are carefully
chosen.
...
... user agent to refresh
its display or reload a resource; its semantics apply only to caching
mechanisms, and such mechanisms need only check a resource's
expiration status when a new request for that resource is initiated.
...
... constraints on their results. Since heuristic expiration
times may compromise semantic transparency, they should be used
cautiously, and we encourage origin servers to provide explicit
expiration times as much as possible.
...
... tag.
o SHOULD send a Last-Modified value if it is feasible to send one,
unless the risk of a breakdown in semantic transparency that could
result from using this date in an If-Modified-Since header would
...
... tags is that only the service author
knows the semantics of a resource well enough to select an
appropriate cache validation mechanism ...
... an entity, or to return it in response to a subsequent request. This
may be because absolute semantic transparency is deemed necessary by
the service author, or because of security ...
... this case, the cache may use either validator in making its own
request without affecting semantic transparency.
However, the choice of validator may affect performance ...
... Informational extensions (those which do not require a change in
cache behavior) may be added without changing the semantics of other
directives. Behavioral extensions are designed to work by acting as
modifiers to the existing base of cache ...
... The Date general-header field represents the date and time at which
the message was originated, having the same semantics as orig-date in
RFC 822std11(-> 2822prop). The field value is an HTTP ...
... entity is generated. In practice, the date can be generated at any
time during the message origination without affecting its semantic
value.
...
... application SHOULD forward the request toward the origin server even
if it has a cached copy of what is being requested. This pragma
directive has the same semantics as the no-cache cache-directive (see
...
... by the response status code. This information is typically, though
not exclusively, used to warn about a possible lack of semantic
transparency from caching operations.
...
... HTTP/1.1. However,
HTTP/1.1 message parsing and semantics are defined by this document
and not the MIME specification.
...