Content Negotiation: Difference between revisions
mNo edit summary |
m (Thexa4 moved page Content Type Negotiation to Content Negotiation) |
(No difference)
| |
Revision as of 07:07, 15 January 2021
A main feature of the HyperText Transfer Protocol (HTTP) is that it allows clients and servers to negotiate what kind of formats both support. They do this using the Accept Header.
This allows implementation of APIs that are Backwards Compatible using Content Negotiation Versioning. Additionally this feature can be used to serve modern image and video formats to clients that indicate support for it.
Mechanism
1. When a client makes a request to a server it supplies all the formats it supports in the Accept Header: Accept: text/html,application/xhtml+xml.
2. The server looks at the list the client sent and excludes all formats it does not support.
3. If there are no common formats, the server either responds with 406 Not Acceptable or it picks a fallback format like text/html.
4. If there are common formats left, the server picks the one the client marked with the highest priority.
5. The server then returns the content that matches the negotiated format.