hi every body,
i've developped a new implementation of fastcgi module for apache.
i'have used the scheme handler of mod_proxy of apache like new mod_proxy_ajp in apache 2.2...
the idea is to make possible proxyfy php application behind apache (for security et and performance...).
to make possible to execute fastcgi in one machine and apache in other machine... separed by firwalle (two DMZ)...
the developpement of the old module as been stoped...
is why i've decide to reimplemente all in new code with decente licence (apache 2 licence...for the moment...)
but in this way php receve all request: image, binary file, static file...and also php file...
for the php file no probleme... but for binary and image... they try to interpret systematicly...
to evitate this i've modify the fastcgi sapi to handle this in the good way...
they only execute by the php interpreter file with a list of extension (.php .php4 .php5...)
all other file are served directly...
i've also modify the sapi to handle index file (index.html index.php...)...
i have some dev to add new parametterer in php.ini to handle this addition...
but after how i can add to php trunck my dev ?
they modify only php cgi/fastcgi sapi !
my code are her: http://mproxyfcgi.sourceforge.net/
Best Regards,
Mathieu
they only execute by the php interpreter file with a list of extension
(.php .php4 .php5...)
Shouldn't it use the MimeType set by httpd.conf/.htaccess ???
E.g., Many users will ForceType a dynamic 'phpscript.png' to output a
GD image.
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?
Making the PHP SAPI extension know how to handle static files does not sound
like the right solution to me. You should be able to redirect the PHP
requests only to PHP's FastCGI (which already works today incl. remotely),
and redirect the static content to a Web Server (thttpd or something alike).
I personally don't see a great reason adding such a patch to PHP itself.
Btw, what are the advantages between your and Apache's FastCGI
implementation? This is something you might want to share with the Apache
httpd folks because if it's a good implementation then it might be nice to
contribute it to them.
Andi
-----Original Message-----
From: Mathieu CARBONNEAUX [mailto:info@ch2o.info]
Sent: Sunday, November 26, 2006 2:59 AM
To: internals@lists.php.net
Subject: [PHP-DEV] new apache fastcgi implementation and php
fastcgi patchhi every body,
i've developped a new implementation of fastcgi module for apache.
i'have used the scheme handler of mod_proxy of apache like
new mod_proxy_ajp in apache 2.2...
the idea is to make possible proxyfy php application behind
apache (for security et and performance...).
to make possible to execute fastcgi in one machine and apache
in other machine... separed by firwalle (two DMZ)...the developpement of the old module as been stoped...
is why i've decide to reimplemente all in new code with
decente licence (apache 2 licence...for the moment...)but in this way php receve all request: image, binary file,
static file...and also php file...
for the php file no probleme... but for binary and image...
they try to interpret systematicly...to evitate this i've modify the fastcgi sapi to handle this
in the good way...
they only execute by the php interpreter file with a list of
extension (.php .php4 .php5...) all other file are served directly...
i've also modify the sapi to handle index file (index.html
index.php...)...i have some dev to add new parametterer in php.ini to handle
this addition...
but after how i can add to php trunck my dev ?they modify only php cgi/fastcgi sapi !
my code are her: http://mproxyfcgi.sourceforge.net/
Best Regards,
Mathieu