[FASTCGI] [PATCH] Updated patch for -pass-header correct handling

Christian Seiler chris_se at gmx.net
Thu Aug 28 00:50:46 EDT 2008


Hi,

I was contacted about my patch for correctly handling the -pass-header
option [1]. It turns out that my patch didn't work with Apache 1.3 - I
just updated it so that it works with Apache 1.3, too.:

http://www.christian-seiler.de/temp/mod_fastcgi-patches/pass-headers.patch

And I somehow can't find my followup posting in the public archives, so
I'll repost the patch for the other issue I had with mod_fastcgi, for
anyone who's interested:

> 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

[1] <http://article.gmane.org/gmane.comp.web.fastcgi.devel/2425>


More information about the FastCGI-developers mailing list