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
charset
Click on the red underlined text to get to the source
... Although HTTP allows an arbitrary token to be used as a charset
value, any token that has a predefined value within the IANA ...
... data MUST be in a form defined above prior to being encoded.
The "charset" parameter is used with some media types to define the
character set ...
... media types to define the
character set (section 3.4) of the data. When no explicit charset
parameter is provided by the sender, media subtypes of the "text"
type are defined to have a default charset ...
... charset
parameter is provided by the sender, media subtypes of the "text"
type are defined to have a default charset value of "ISO-8859-1" when
received via HTTP ...
... character sets other than "ISO-8859-1" or
its subsets MUST be labeled with an appropriate charset value.
Some HTTP/1.0 ...
... Content-Type header without
charset parameter incorrectly to mean "recipient should guess."
Senders wishing to defeat this behavior MAY include a charset
parameter ...
... charset parameter incorrectly to mean "recipient should guess."
Senders wishing to defeat this behavior MAY include a charset
parameter even when the charset is ISO-8859-1 and SHOULD do so when
...
... Senders wishing to defeat this behavior MAY include a charset
parameter even when the charset is ISO-8859-1 and SHOULD do so when
it is known that it will not confuse the recipient.
...
... HTTP/1.0 clients did not deal properly with
an explicit charset parameter. HTTP/1.1 recipients MUST respect the
charset ...
... charset parameter. HTTP/1.1 recipients MUST respect the
charset label provided by the sender; and those user agents that have
...
... sender; and those user agents that have
a provision to "guess" a charset MUST use the charset from the
content-type ...
... user agents that have
a provision to "guess" a charset MUST use the charset from the
content-type field if they support that charset ...
... charset from the
content-type field if they support that charset, rather than the
recipient's preference, when initially displaying a document.
...
... request-header = Accept ; Section 14.1
| Accept-Charset ; Section 14.2
| Accept-Encoding ; Section 14.3
...
... user agent
capabilities and user preferences: Accept (section 14.1), Accept-
Charset (section 14.2), Accept-Encoding (section 14.3), Accept-
Language ...
... Accept-Charset ...
...
Character set values are described in section 3.4. Each charset may
be given an associated quality value which represents the user's
preference for that charset ...
... charset may
be given an associated quality value which represents the user's
preference for that charset. The default value is q=1. An example is
...
... unicode-1-1;q=0.8
If no Accept-Charset header is present, the default is that any
character set ...
... header is present, the default is that any
character set is acceptable. If an Accept-Charset header is present,
and if the server cannot send a response which is acceptable
...
... header is present,
and if the server cannot send a response which is acceptable
according to the Accept-Charset header, then the server SHOULD send
an error response ...