Re: mod_proxy_fcgi and php
On 5/13/06, Markus Schiegl <[EMAIL PROTECTED]> wrote: Because of r->uri == r->path_info, ap_add_cgi_vars sets SCRIPT_NAME to "" PHP needs this one for backreference and http://cgi-spec.golux.com states it must be set. An empty r->path_info (manually patched) would give me a SCRIPT_NAME but removes PATH_INFO, ergo no solution. Ideas? What do other fcgi implementations send? When in doubt, I imagine the best thing to do is whatever mod_fastcgi or mod_fcgid do. Each fcgi-request is logged (mod_proxy_fcgi.c, line 918) as error? What about replacing APLOG_ERR with APLOG_DEBUG? Done, along with changing a couple of APLOG_DEBUGs that are really errors to APLOG_ERR. -garrett
RE: mod_proxy_fcgi and php
On 10/05/06, Garrett Rooney wrote: My next round with mod_proxy_fcgi and PHP as backend... > Sorry it took me so long to get back to this. Got distracted > with other things, etc. dito. > > From my limited perspective r->filename should be set to > > "/opt/www/html/i.php" Any ideas? > > mod_proxy_fcgi is talking to an arbitrary socket that could > correspond to any file on disk, how would it figure out what > to set r->filename to? The more i think about this, the more i agree with you. speeking to a network connected backend and passing infos about local files (actually not needed) makes little sense. Other conclusion: there is no based security possible, hence i switched to based security. two more questions: Because of r->uri == r->path_info, ap_add_cgi_vars sets SCRIPT_NAME to "" PHP needs this one for backreference and http://cgi-spec.golux.com states it must be set. An empty r->path_info (manually patched) would give me a SCRIPT_NAME but removes PATH_INFO, ergo no solution. Ideas? Each fcgi-request is logged (mod_proxy_fcgi.c, line 918) as error? What about replacing APLOG_ERR with APLOG_DEBUG? > > While playing with mod_rewrite i realized it does not recognize fcgi > > as scheme yet (1) The following patch should solve this. ... > > I'll look at getting this checked in, thanks! thanks! -- Markus Schiegl | [EMAIL PROTECTED] | [EMAIL PROTECTED] | PGP-KeyID: 0x21063504
Re: mod_proxy_fcgi and php
On 4/22/06, Markus Schiegl <[EMAIL PROTECTED]> wrote:
Sorry it took me so long to get back to this. Got distracted with
other things, etc.
From my limited perspective r->filename should be set to
"/opt/www/html/i.php"
Any ideas?
mod_proxy_fcgi is talking to an arbitrary socket that could correspond
to any file on disk, how would it figure out what to set r->filename
to?
The fact that PHP has settings you can tweak to make this work implies
to me that it's not a problem we need to fix...
While playing with mod_rewrite i realized it does not recognize fcgi as
scheme yet (1)
The following patch should solve this.
Index: httpd-trunk/modules/mappers/mod_rewrite.c
===
--- httpd-trunk/modules/mappers/mod_rewrite.c (revision 396157)
+++ httpd-trunk/modules/mappers/mod_rewrite.c (working copy)
@@ -577,6 +577,9 @@
if (!strncasecmp(uri, "tp://", 5)) {/* ftp://*/
return 6;
}
+if (!strncasecmp(uri, "cgi://", 6)) { /* fcgi://*/
+return 7;
+}
break;
case 'g':
I'll look at getting this checked in, thanks!
-garrett
