Eric,
Thanks for your response. That's sort of what I figured since processing is
handed over to fcgi to complete the request then httpd has no control at
that point, and any response headers that were set before by httpd could
be overwritten. The strange thing is that I have a similar block of code
on a mod_php server that isn't working either. I have found numerous
resourced online that say a 'Header set Content-type "text/css"'
directive should work for a regular old mod_php setup.
-Ross
----- Original Message -----
From: Eric Covener <covener@xxxxxxxxx>
To: users@xxxxxxxxxxxxxxxx
Date: Wed, 23 May 2012 13:44:27 -0400
Subject: Re: mod_fcgid setting content-type header
> > The only approach I've found that works is to
> > stick a header("Content-type: text/css") at the top of my css files,
which
> > is inconvenient to say the least. Anyone have a solution for this?
>
> Most of those *type directives only apply when apache serves a static
> file by that name. If you're generating it from fcgi, you have to
> issue the content-type yourself.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|