3 7 3 7 1 transfer updating
This field allows clients capable of understanding more comprehensive or special- purpose character sets to signal that capability to a server which is capable of representing documents in those character sets. Each charset MAY be given an associated quality value which represents the user's preference for that charset. An example is The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is not mentioned elsewhere in the Accept-Charset field.
If no "*" is present in an Accept-Charset field, then all character sets not explicitly mentioned get a quality value of 0, except for ISO-8859-1, which gets a quality value of 1 if not explicitly mentioned.
The prefix rule simply allows the use of prefix tags if this is the case.
The language quality factor assigned to a language-tag by the Accept-Language field is the quality value of the longest language- range in the field that matches the language-tag.
Each media-range MAY be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor.
The first "q" parameter (if any) separates the media-range parameter(s) from the accept-params.
If an Accept-Encoding field is present in a request, and if the server cannot send a response which is acceptable according to the Accept-Encoding header, then the server SHOULD send an error response with the 406 (Not Acceptable) status code.
Note: This use of a prefix matching rule does not imply that language tags are assigned to languages in such a way that it is always true that if a user understands a language with a certain tag, then this user will also understand all languages with tags for which this tag is a prefix.
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.
The Accept request-header field can be used to specify certain media types which are acceptable for the response.
Accept headers can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request for an in-line image.