From: "Christoph Schneegans" <[EMAIL PROTECTED]> Sent: Tuesday, February 19, 2002 3:56 PM
> <http://httpd.apache.org/docs/content-negotiation.html> explains how to > use qs parameters in a type map file to assign a source quality to the > different variants. It does not explain how to use qs values in > conjunction with MultiViews > However, it seems to be possible, using the AddType directive: > > AddType image/svg;qs=0.85 svg svgz > AddType image/png;qs=0.7 png > AddType image/jpeg;qs=0.8 jpg jpeg > > This works as expected but I'm concerned about the Content-Type headers > that are transmitted to the client: > > Content-Type: image/svg;qs=0.85 > Content-Type: image/png;qs=0.7 > Content-Type: image/jpeg;qs=0.8 > > In contrast to negotiation via type map, the qs values are included in > the response header. Good concern, they are invalid. Multiviews was never hacked to decode the qs value [nor were mime or the core.] The patch to do so is not trivial, but is [IMHO] very worthwhile. Bill
