RFC 2068:Hypertext Transfer Protocol -- HTTP/1.1
RFC-Ref

content negotiation


Click on the red underlined text to get to the source

... An entity included with a response that is subject to content negotiation, as described in section 12. There may exist multiple representations associated with a particular response status. ...
... representations associated with a particular response status. content negotiation The mechanism for selecting the appropriate representation when servicing a request, as described in section 12. The ...
... representations is termed a `variant.' Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation. client ...


... HTTP content negotiation (section 12) uses short "floating point" numbers to indicate the relative importance ("weight") of various ...


... Content Negotiation ...
... entity types. For that reason, HTTP has provisions for several mechanisms for "content negotiation" -- the process of selecting the best representation for a given response ...
... error responses. There are two kinds of content negotiation which are possible in HTTP: server-driven and agent ...
... requirements described in section 13.6 that describes the interactions between caching and content negotiation. ...


... Use of server-driven content negotiation (section 12), as indicated by the presence of a Vary header field in a response, alters the ...



Google
Web
RFC-Ref