|Summary:||want directive for setting content negotiation quality (qs)|
|Product:||Apache httpd-2||Reporter:||John Belmonte <john>|
|Component:||mod_negotiation||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description John Belmonte 2004-06-08 18:54:53 UTC
In brief, I would like a directive for setting the qs value for a resource. Synopsis: <Files index.rss> SetQs .1 </Files> I know that it is possible to set the qs value using a type map, but it's a burden to maintain such a configuration for the following reasons: 1) every variant must have an entry in the type map, even if you want to set the Qs on just one file 2) each variant entry must spell out the content type, even though it is ignored when the resource is located in a file (mentioned in Bug 29445). An example use case is when you would like to publish an .rss variant of a resource. The problem is that certain poorly maintained browsers, and even the validator.org validator, don't bother specifying which types they expect, and so the .rss file might be served to them. A reasonable solution is to lower the qs value for the .rss variant. Currently, for the directory index, I have to make a map file like this: URI: index URI: index.rss Content-type: application/rss+xml; qs=.1 URI: index.en.html Content-type: text/html URI: index.fr.html Content-type: text/html . . . Obviously that's difficult to maintain if you have many variants of a resource. I would much rather just set the qs of index.rss, as shown at the beginning of this report.
Comment 1 John Belmonte 2004-06-08 21:39:54 UTC
In the example I gave, it turns out that the map file must be even more verbose and redundant, as it seems that Content-language must be provided for each item in order for content negotiation to work: URI: index URI: index.rss Content-type: application/rss+xml; qs=.1 Content-language: en URI: index.en.html Content-type: text/html Content-language: en URI: index.fr.html Content-type: text/html Content-language: fr . . .
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:51 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.