Bug 44657 - prefer-type, -encoding, and -charset cookie? (as prefer-language)
Summary: prefer-type, -encoding, and -charset cookie? (as prefer-language)
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_negotiation (show other bugs)
Version: 2.2.4
Hardware: PC Linux
: P2 enhancement with 3 votes (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2008-03-22 14:43 UTC by Da’an
Modified: 2018-11-07 21:08 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Da’an 2008-03-22 14:43:32 UTC
Taken from the example were the Accept-Language (and it qualifiers) HTTP  header is overridden by a cookie set in the user’s browser; from http://httpd.apache.org/docs/2.2/content-negotiation.html#better :
SetEnvIf Cookie "lang=(.+)" prefer-language=$1 Header append Vary cookie

I wish this could be done this be done with other Accept HTTP headers as well. By introducing other enviromental variables—such as prefer-type, prefer-encoding, and prefer-charset—they can be used to override other default  negotiation methods for the Content-Type, Content-Encoding, and Content-Charset headers. I had visioned something like the below:
SetEnvIf Cookie "type=(.+)" prefer-type=$1 Header append Vary cookie
SetEnvIf Cookie "charset=UTF-8" prefer-type=utf8 Header append Vary cookie

Basically I want to offer the user a way to override the default content negotiation method. Like with the prefer-language option. For web browsers that does not spesicfy supported charsets, types, encodings, etc.

I mean to put an option to set override cookies on the 406 error ducoument page. So users can fill in the blanks for their browsers.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:31 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.