Bug 149596

Summary:	Enable FastCGI in standalone /usr/bin/php
Product:	[Fedora] Fedora	Reporter:	Matthias Saou <matthias>
Component:	php	Assignee:	Joe Orton <jorton>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	rdieter
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://www.lighttpd.net/documentation/fastcgi.html
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-07-05 15:30:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthias Saou 2005-02-24 12:07:46 UTC

Hi,

I'm currently using lighttpd with PHP through FastCGI. It works
amazingly well, and lighttpd is now part of Fedora Extras. But in
order to have FastCGI support compiled in the /usr/bin/php standalone
binary (in addition to regular CGI which still works), one needs to
change the following in the spec file and rebuild :

 # Build standalone /usr/bin/php
 pushd build-cgi
-build --enable-force-cgi-redirect
+build --enable-force-cgi-redirect \
+      --enable-fastcgi \
+      --enable-discard-path \


Would it be possible to make this change to the main php package for
everyone to benefit from it and be able to use FastCGI out-of-the-box?
I don't know the exact implications or consequences regarding the
binary, but it still works fine from the command-line for me and
states that is has both CGI and FastCGI enabled. Also, there is no
possible consequence on the mod_php version, which is what the vast
majority of people use.

Comment 1 Matthias Saou 2005-03-30 12:00:05 UTC

Joe, any idea if this change could be done before the next FC4 test release? If
it doesn't break anything, it would be really great to have it be in the default
build.

Comment 2 Joe Orton 2005-03-30 14:02:33 UTC

I'm not really sure it's really appropriate to enable this by default, since we
don't ship a web server (or module) which can speak FastCGI in Core itself; it
looks like a fair chunk of extra code to build in.

Comment 3 Matthias Saou 2005-03-30 14:12:46 UTC

But enabling software in Extras to play well with Core is something that is
wanted nevertheless, no? Especially since a FastCGI-enabled php in Extras is not
going to happen.

If this change affected mod_php in any way, I'd be much less keen on suggesting
it. But it affects only the standalone /usr/bin/php binary which very few people
use (I know I do only for a few cron jobs), but that many could start using if
it worked with FastCGI.

Comment 4 Matthias Saou 2005-04-25 08:54:34 UTC

Now that there are two separate standalone binaries (one for CLI, and the other
for CGI), wouldn't it be even safer to enable FastCGI in the CGI one?

Comment 5 Joe Orton 2005-04-25 10:31:04 UTC

Yes OK I submit :) I've enabled FastCGI support in /usr/bin/php-cgi in 5.0.4-7;
can you test it and let me know whether it works? I don't have a FastCGI setup
handy...