Re: qs values in conjunction with MultiViews

2002-02-19 Thread William A. Rowe, Jr. 

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

Re: qs values in conjunction with MultiViews

2002-02-19 Thread Christoph Schneegans 

William A. Rowe, Jr wrote:

[qs values in AddType directives and Content-Type headers]

 Good concern, they are invalid.

Okay, that's a clear statement. Thanks.

  Multiviews was never hacked to decode the qs value [nor were mime or the 
 core.]

But qs values do affect Multiviews! The only task would be to remove them
from the response header. Please take a look at
http://schneegans.de/temp/qs-multiviews. Using IE or Opera, you'll see the
HTML variant. Using Mozilla, you'll see the XHTML variant. The .htaccess 
file only contains these directives:

  Options +MultiViews
  AddType text/html;charset=iso-8859-1;qs=1.000 .html
  AddType application/xhtml+xml;iso-8859-1;qs=0.999 .xhtml


Best regards,
Christoph Schneegans