Re: Serving Images via FastCGI

No, the script does not send content-length, although the image is static. I cannot
change the application,  only its running environment. Would sending content-length
somehow alter FastCGI's behaviour? If it was up to me, I would not serve static
images via a script, that's just uncalled for. The script is a commercial PHP app
chosen by a client, I'm just an admin. I'm aware of clients caching content based
on HTTP's 1.1 caching semantics, but I don't see how this would change anything.
Even if client just requests and reads the headers, it still needs to make a request
to the FastCGI process.

-Simon

On Wed, 31 Jan 2007 00:17:45 +0000, Chris Lightfoot wrote:

>On Tue, Jan 30, 2007 at 03:18:32PM -0500, Simon wrote:
>> I have a PHP application which loads images via PHP script. Running this PHP
>> script via PHP FastCGI creates a problem. The application loads hundreds of
>> small images via this script on a single .php page This invokes hundreds of
>> FastCGI processes just to serve a single user.  When images are served via 
>> Apache, only 2 processes are used to serve all the images for a single HTTP
>> keep-alive session in a series manner instead of parallel in case of FastCGI. Is
>> there a way to implement same keep-alive mechanism in the case of a FastCGI
>> app serving images during single HTTP keep-alive session?

>does your PHP script send content-length headers? does it
>implement the HTTP cacheing semantics? have you tried
>replacing it with an implementation in a different
>language? why are you serving images from a script anyway?

>-- 
>``Americans' greatest fear is that America will turn out
>  to have been a phenomenon, not a civilization.'' (Shirley Hazzard)





___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/