Re:The Accept Header
by masklinn on Monday December 19, 2011 @02:46AM
(#3368879)
> That text/html should be preferred to text/plain even though both would end up with a quality of 1.0. Although there's no actual algorithm defined for dealing with this situation. The entire decision tree is left implicit based on the examples provided.
It does a bit more than show example in passing, it specifies the following:
> Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies to a given type, the most specific reference has precedence.
And indicates how precedence works: accept extensions > "full" mime > type/wildcard > wildcard.
The only situation which is not defined out is a type/wildcard with an extension.
This tie-breaker happens after quality-based precedence resolution.
(full agreement on Accept headers of browsers, they're completely bonkers)
It does a bit more than show example in passing, it specifies the following:
> Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies to a given type, the most specific reference has precedence.
And indicates how precedence works: accept extensions > "full" mime > type/wildcard > wildcard.
The only situation which is not defined out is a type/wildcard with an extension.
This tie-breaker happens after quality-based precedence resolution.
(full agreement on Accept headers of browsers, they're completely bonkers)