Re: [PATCH] Incorrect handling of -pass-header
Christian Seiler <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel,gmane.spam.detected |
|---|---|
| Message-ID | <[email protected]> |
Hi, > ["HTTP_AUTHORIZATION" vs "Authorization" with -pass-header] > I attached a patch against mod_fastcgi 2.4.6 that will create the > correct environment variable instead. What's the status of this issue? Just for the record, here's the patch again: http://www.christian-seiler.de/temp/mod_fastcgi-patches/pass-headers.patch Also, I discovered another issue with mod_fastcgi: If a CGI script sends two 'Status: ' headers, mod_fastcgi will cause an internal server error. Yes, it may not be a very good idea to send two status lines BUT a) the CGI specification does not forbid it explicitely and b) Apache does not complain when this happens with normal CGI scripts. As I see no reason to enforce such strictness (Apache with normal CGI doesn't, lighttpd with FastCGI doesn't) and I came across a few scripts that caused this kind of problem with mod_fastcgi, here's a patch that removes the duplicate header check: http://www.christian-seiler.de/temp/mod_fastcgi-patches/duplicate-allowed.patch Regards, Christian ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/