From f05a6c1db92cd1984c35d29e8be30de5d97aaee9 Mon Sep 17 00:00:00 2001
From: Joshua Slive would indicate that any type starting "image/" is acceptable,
- as is any other type (so the first "image/*" is redundant).
+ as is any other type.
Some browsers routinely send wildcards in addition to explicit
types they can handle. For example:Accept: image/*, */*
The intention of this is to indicate that the explicitly listed types are preferred, but if a different representation is - available, that is ok too. However under the basic algorithm, - as given above, the */* wildcard has exactly equal preference - to all the other types, so they are not being preferred. The - browser should really have sent a request with a lower quality - (preference) value for *.*, such as:
+ available, that is ok too. Using explicit quality values, + what the browser really wants is something like:
Accept: text/html, text/plain, image/gif, image/jpeg, */*; q=0.01
would indicate that any type starting "image/" is acceptable, - as is any other type (so the first "image/*" is redundant). + as is any other type. Some browsers routinely send wildcards in addition to explicit types they can handle. For example:
@@ -404,11 +404,8 @@The intention of this is to indicate that the explicitly listed types are preferred, but if a different representation is - available, that is ok too. However under the basic algorithm, - as given above, the */* wildcard has exactly equal preference - to all the other types, so they are not being preferred. The - browser should really have sent a request with a lower quality - (preference) value for *.*, such as:
+ available, that is ok too. Using explicit quality values, + what the browser really wants is something like: