-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
so a while ago i tested FastCGI PHP instead of PHP CGI. unfortunately it had a few problems, particularly with long-running scripts.
it's now possible to enable this selectively for particular files/directories. read https://wiki.toolserver.org/view/Switchboard to find out how.
please do this if you can, as it should help significantly with load on hemlock.
- river.
Is this an alternative implementation of CGI or an alternative implementation of PHP?
On Wed, Jul 23, 2008 at 6:31 AM, River Tarnell river@wikimedia.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
so a while ago i tested FastCGI PHP instead of PHP CGI. unfortunately it had a few problems, particularly with long-running scripts.
it's now possible to enable this selectively for particular files/directories. read https://wiki.toolserver.org/view/Switchboard to find out how.
please do this if you can, as it should help significantly with load on hemlock.
- river.-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (SunOS)
iEYEARECAAYFAkiHCGYACgkQIXd7fCuc5vLQ+QCgjOuPN40SLpaD0BSU0TN7mXEk 4ZgAoJv251HiADIy5UJxqtQNzN1WRSK6 =7l6e -----END PGP SIGNATURE-----
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
James Hare:
Is this an alternative implementation of CGI or an alternative implementation of PHP?
FastCGI [0] is an alternative to CGI. PHP supports both CGI and FastCGI.
- river.
[0] http://en.wikipedia.org/wiki/FastCGI
River says it's CGI and Minute says it's PHP.
On Wed, Jul 23, 2008 at 7:29 AM, MinuteElectron < minuteelectron@googlemail.com> wrote:
James Hare wrote:
Is this an alternative implementation of CGI or an alternative implementation of PHP?
The later.
MinuteElectron.
Toolserver-l mailing list Toolserver-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/toolserver-l
2008/7/23 River Tarnell river@wikimedia.org:
read https://wiki.toolserver.org/view/Switchboard to find out how.
The second way seems to rely on "AddHandler" for .php files. I sometimes use rewrite rules to hide the ugly-looking file extension completely, does the described .htaccess in public_html affect them?
— Kalan
Kalan schrieb:
2008/7/23 River Tarnell river@wikimedia.org:
read https://wiki.toolserver.org/view/Switchboard to find out how.
The second way seems to rely on "AddHandler" for .php files. I sometimes use rewrite rules to hide the ugly-looking file extension completely, does the described .htaccess in public_html affect them?
— Kalan
If you want to rewrite Foo.php to Foo.phpf or Foo to Foo.phpf or bothor whatever is up to you. The example of rewriting Foo.php to Foo.phpf is just to show how to let old URLs ending with .php remain functional. The important bit is that the actual file path (right side of the rewrite rule) is phpf.
Using AddHandler works fine if you want to do it for all files in a directory that have a given extension, e.g. .php. I tried to apply it to a full file name, but that doesn't seem to work - it likes only file extensions, and thus can not be used for individual files. This is a bit silly, but apparently, we have to live with it :)
-- daniel
On Jul 23, 2008, at 9:18 AM, Daniel Kinzler wrote:
Kalan schrieb:
2008/7/23 River Tarnell river@wikimedia.org:
read https://wiki.toolserver.org/view/Switchboard to find out how.
The second way seems to rely on "AddHandler" for .php files. I sometimes use rewrite rules to hide the ugly-looking file extension completely, does the described .htaccess in public_html affect them?
— Kalan
If you want to rewrite Foo.php to Foo.phpf or Foo to Foo.phpf or bothor whatever is up to you. The example of rewriting Foo.php to Foo.phpf is just to show how to let old URLs ending with .php remain functional. The important bit is that the actual file path (right side of the rewrite rule) is phpf.
Using AddHandler works fine if you want to do it for all files in a directory that have a given extension, e.g. .php. I tried to apply it to a full file name, but that doesn't seem to work - it likes only file extensions, and thus can not be used for individual files. This is a bit silly, but apparently, we have to live with it :)
-- daniel
You should be able to limit to specific files by wrapping the AddHandler directives in <Files> (or similar) elements. See http://httpd.apache.org/docs/2.0/mod/core.html#files (I guessed at apache version because the Server header served by the toolserver doesn't specify a version. Apache 1.3 equivalent doc: http:// httpd.apache.org/docs/1.3/mod/core.html#files ) See also: http://httpd.apache.org/docs/2.0/sections.html#file-and-web (or http://httpd.apache.org/docs/1.3/sections.html )
Also, general note: I don't have a toolserver account so if there's something specific to the toolserver I might be a little off.
--jeremy
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Kalan:
2008/7/23 River Tarnell river@wikimedia.org: The second way seems to rely on "AddHandler" for .php files. I sometimes use rewrite rules to hide the ugly-looking file extension completely, does the described .htaccess in public_html affect them?
no, it is identical to the way existing .php files work, which uses AddHandler anyway.
- river.
toolserver-l@lists.wikimedia.org