Start Dating header

Dating header

Each media-range MAY be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor.

In this case, if "identity" is one of the available content-codings, then the server SHOULD use the "identity" content-coding, unless it has additional information that a different content-coding is meaningful to the client.

"gzip" and "compress") are preferred; some older clients improperly display messages sent with other content-codings.

This section defines the syntax and semantics of all standard HTTP/1.1 header fields.

For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who receives the entity.

If an Accept-Language header is present, then all languages which are assigned a quality factor greater than 0 are acceptable.

It might be contrary to the privacy expectations of the user to send an Accept-Language header with the complete linguistic preferences of the user in every request.

However, unless the user agent is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.

The Accept-Charset request-header field can be used to indicate what character sets are acceptable for the response.

Future media types are discouraged from registering any parameter named "q".

SHOULD be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in quality." If no Accept header field is present, then it is assumed that the client accepts all media types.

The prefix rule simply allows the use of prefix tags if this is the case.