Bug 44656 - Tries to retrive error document 404 instead of 406 when negotiation fails
Summary: Tries to retrive error document 404 instead of 406 when negotiation fails
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_negotiation (show other bugs)
Version: 2.2.4
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2008-03-22 12:51 UTC by Da’an
Modified: 2018-11-07 21:09 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 12:51:55 UTC
I looked trough my error logs and discovered this problem:
> Negotiation: discovered file(s) matching
> request: /var/www/organservice/organrepairs (None could be negotiated). 
> File does not exist: /var/www/shared/errors/404
This happend at the same time from the same host/user.

Should not this have trigger a 406 Negotiation Failed responds instead of 
a 404 Not Found? Apache understands that the request could not be 
negotiated, but the next line says it did not find the not found error 

My configuration clarly spesifies “ErrorDocument 
406 /var/www/shared/errors/406” which does exist. The 404 page, 
ironically enough, does not exsist. The error documents must be 
Comment 1 Nick Kew 2008-03-22 13:29:20 UTC
In principle I think you're right.  However, a 406 response should also send a list of available variants, and the code for that doesn't seem (at a glance) to be implemented, so it's not quite a trivial change.

Are you getting this error when you'd expect something different, such as selecting an available variant?  Or is it just the response code that's wrong?
Comment 2 Da’an 2008-03-22 13:39:37 UTC
I would expect it to negotiate or send a 406 document with a list (generated by PHP and exec("ls")) of available variants. (Or the default 406 error.) I would not expect it to try to retrieve the 404 error document instead.
Comment 3 William A. Rowe Jr. 2018-11-07 21:09:39 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.