Accept request HTTP header advertises which content types, expressed as MIME types, the client is able to understand. Using content negotiation, the server then selects one of the proposals, uses it and informs the client of its choice with the
Content-Type response header. Browsers set adequate values for this header depending on the context where the request is done: when fetching a CSS stylesheet a different value is set for the request than when fetching an image, video or a script.
// Multiple types, weighted with the quality value syntax:
Accept: text/html, application/xhtml+xml, application/xml;q=0.9, image/webp, */*;q=0.8
- A single, precise MIME type, like
- A MIME type, but without any subtype.
image/* will match
image/gif and any other image types.
- Any MIME type
;q= (q-factor weighting)
- Any value used is placed in an order of preference expressed using relative quality value called the weight.
Accept: text/html, application/xhtml+xml, application/xml;q=0.9, */*;q=0.8
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
Update compatibility data on GitHub
Yes||Samsung Internet Android
- Full support
Schlagwörter des Dokuments und Mitwirkende