Accept-Charset
E290850
Accept-Charset is an HTTP request header that tells the server which character encodings the client is able to understand and prefers.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Accept-Charset canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2703270 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Accept-Charset Context triple: [RFC 2068, definesHeaderField, Accept-Charset]
-
A.
Accept-Encoding
Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
-
B.
Accept-Language
Accept-Language is an HTTP request header used to indicate the preferred natural languages for the response content.
-
C.
UTF-8
UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
-
D.
ASCII
ASCII is a widely used character encoding standard that represents text in computers and other devices using 7-bit numerical codes for letters, digits, punctuation, and control characters.
-
E.
Content-Encoding
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Accept-Charset Target entity description: Accept-Charset is an HTTP request header that tells the server which character encodings the client is able to understand and prefers.
-
A.
Accept-Encoding
Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
-
B.
Accept-Language
Accept-Language is an HTTP request header used to indicate the preferred natural languages for the response content.
-
C.
UTF-8
UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
-
D.
ASCII
ASCII is a widely used character encoding standard that represents text in computers and other devices using 7-bit numerical codes for letters, digits, punctuation, and control characters.
-
E.
Content-Encoding
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP header field
ⓘ
HTTP request header ⓘ |
| appliesTo | HTTP client ⓘ |
| canBeOmitted | yes ⓘ |
| canContainToken |
*
ⓘ
charset name ⓘ |
| commonlyUsedWith |
Accept
ⓘ
Accept-Encoding ⓘ Accept-Language ⓘ Content-Type ⓘ |
| defaultBehavior | if header is absent, any charset is acceptable to the client ⓘ |
| definedInSpecification | RFC 2616 ⓘ |
| deprecationReason | UTF-8 is now recommended as the default and only charset for most modern HTTP APIs ⓘ |
| exampleClient |
HTTP library
ⓘ
web browser ⓘ |
| exampleServerBehavior | server may choose the highest q-value charset it supports ⓘ |
| fieldName | Accept-Charset ⓘ |
| fieldNameCase | case-insensitive ⓘ |
| governedBy | HTTP header field rules ⓘ |
| governs | representation character encoding ⓘ |
| headerCategory | content negotiation header ⓘ |
| headerType | request header ⓘ |
| ifNoAcceptableCharset | server may respond with 406 Not Acceptable ⓘ |
| influences |
selection of response character encoding
ⓘ
server content negotiation ⓘ |
| interpretedBy | HTTP server ⓘ |
| introducedIn | HTTP/1.1 ⓘ |
| layer | application layer ⓘ |
| parameterPurpose | q parameter expresses relative quality factor (preference) ⓘ |
| purpose |
to express client preferences for character encodings
ⓘ
to indicate which character encodings the client can understand ⓘ |
| qualityFactorDefault | 1.0 when q is not specified ⓘ |
| qualityFactorRange | 0 to 1 ⓘ |
| relatedConcept |
character encoding
ⓘ
charset parameter of Content-Type ⓘ content negotiation ⓘ |
| relatedToSpecification | RFC 7231 ⓘ |
| status | deprecated in HTTP/1.1 semantics ⓘ |
| syntaxExample |
Accept-Charset: iso-8859-1, utf-8;q=0.7, *;q=0.7
ⓘ
Accept-Charset: utf-8 ⓘ |
| typicalCharset |
iso-8859-1
ⓘ
utf-8 ⓘ |
| usedInProtocol | HTTP ⓘ |
| usesParameter | q ⓘ |
| valueType |
comma-separated list
ⓘ
weighted values with quality factors ⓘ |
| wildcardMeaning | * means any character set is acceptable ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Accept-Charset Description of subject: Accept-Charset is an HTTP request header that tells the server which character encodings the client is able to understand and prefers.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.