Re: SetHandler and AddHandler ignored

I'm afraid your barking up the wrong tree.  SetHandler/AddHandler don't set
the content-type.

Is your fastcgi application sending a content-type header?

Rob

> -----Original Message-----
> From: fastcgi-developers-bounces+robs=fastcgi.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> [mailto:fastcgi-developers-bounces+robs=fastcgi.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org]
> On Behalf Of David Pashley
> Sent: Monday, September 29, 2008 3:38 AM
> To: fastcgi-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> Subject: [FASTCGI] SetHandler and AddHandler ignored
> 
> I've been looking at a problem I've been having with using
> FastCGIExternalServer. The problem is that it ignores SetHandler and
> AddHandler and passes everything through the fastcgi handler. I've
> tracked this down to the fixups() function in mod_fastcgi.c, which looks
> to see if the path is in one of the fastcgi handled paths and explicitly
> sets the handler to fastcgi-script. This causes a problem when using php
> in fastcgi mode, as the module forces every single request through the
> php interpreter, rather than just the php files. The result is that
> every request ends up having a content type of text/html.
> 
> The fixups() function was added some time between 22-Sep-2002 and
> 19-Oct-2002 with the change log entry of:
> 
>  *) Eliminate the need for SetHandler or AddHandler with static or
>      external applications.
> 
> The solution would be to remove the fixups function and document that if
> a users wants the old behaviour, they should add a Sethandler
> fastcgi-script option in their apache config.
> 
> I can provide a patch if needs be.
> 
> --
> David Pashley
> [email protected]
> Nihil curo de ista tua stulta superstitione.
> _______________________________________________
> FastCGI-developers mailing list
> FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers