Bug 50891 - Apache rewrites WWW-Authenticate headers from CGI programs
Summary: Apache rewrites WWW-Authenticate headers from CGI programs
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_cgi (show other bugs)
Version: 2.2.16
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-03-08 09:24 UTC by alec-keyword-apache.d8a97a
Modified: 2018-11-07 21:09 UTC (History)
0 users

patch to preserve WWW-authenticate headers in CGI responses (1.61 KB, application/octet-stream)
2011-03-08 09:24 UTC, alec-keyword-apache.d8a97a

Note You need to log in before you can comment on or make changes to this bug.
Description alec-keyword-apache.d8a97a 2011-03-08 09:24:55 UTC
Created attachment 26743 [details]
patch to preserve WWW-authenticate headers in CGI responses

When parsing CGI response headers, apache rewrites the WWW-Authenticate headers in a standards-compliant way.  Unfortunately, popular browsers (Firefox 3.6.15 at least) do not correctly process the rewritten headers.  This breaks completely breaks authentication when multiple WWW-Authenticate headers are sent from a CGI script.

There is already code to preserve Set-Cookie headers in util_script.c.  Replicating this code for WWW-Authenticate fixes the issue.

The attached patch implements this fix in the most trivial way.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:22 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.