Running PHP Scripts on the CS Webservers

The multi-user nature of the CS webservers require us to run PHP in a slightly uncommon way. We run PHP as a CGI using Apache's mod_fcgid FastCGI module. That means that some common ways to use PHP need to be done slightly differently in our environment. These differences are documented below.

Files in Your Home Directory

There is a php-cgi script in your ~/public_html/cgi-bin directory. This is the script that runs the PHP CGI interpreter for you. Apache is told about this script by the FcgidWrapper directive in your ~/public_html/.htaccess file.

Changing either of these files should be done with care, as doing so could prevent PHP from working for your webpages.

Apache AddType Directives

The CS webservers treat any file that has a .php extension as a PHP script. In some cases, you might want files with other extensions to also be treated as PHP scripts.

Most documentation on the web describes how to use the AddType Apache directive in your .htaccess file for this, and that directive usually looks like this:

AddType application/x-httpd-php .html

However, for our websites, instead of AddType, you will need to use the AddHandler directive to process the file as a FastCGI script and give the full path to your php-cgi script to run it. For example, a grad account might use the following to execute HTML files at PHP scripts:

AddHandler fcgid-script .html
FcgidWrapper /users/YOUR-ACCOUNT-HERE/public_html/cgi-bin/php-cgi .html

A ugrad account might use the following to execute files with a ".p" extension as PHP scripts:

AddHandler fcgid-script .p
FcgidWrapper /home/YOUR-ACCOUNT-HERE/public_html/cgi-bin/php-cgi .p

Apache ForceType Directives

Another way to force a particular file or files to be treated as PHP is to use a <Files> or <Directory> section in your .htaccess file to target those files specifically. The customary documentation on the web uses the ForceType directive for this:

<Files quux.foo>
   ForceType application/x-httpd-php
</Files>

However, for our websites, instead of ForceType, you have to use the SetHandler directive along with the full path to your php-cgi script. For a grad example:

<Files quux.foo>
  SetHandler fcgid-script
  FcgidWrapper /users/YOUR-ACCOUNT-HERE/public_html/cgi-bin/php-cgi
</Files>

ugrad accounts, need to use a slightly different path:

<Files quux.foo>
  SetHandler fcgid-script
  FcgidWrapper /home/YOUR-ACCOUNT-HERE/public_html/cgi-bin/php-cgi
</Files>

If PHP Doesn't Work

First, check to make sure your ~/public_html/.htaccess and ~/public_html/cgi-bin/php-cgi files exist and have the right contents and permissions.

For grad accounts, ~/public_html/.htaccess should contain the following line:

FcgidWrapper /users/your-account/public_html/cgi-bin/php-cgi .php

For ugrad accounts, ~/public_html/.htaccess should contain the following line:

FcgidWrapper /home/your-account/public_html/cgi-bin/php-cgi .php

Make sure you replace "your-account" with your actual account name.

~/public_html/cgi-bin/php-cgi should have the following contents:

#!/bin/sh
exec /usr/bin/php-cgi

All of the files need to have specific permissions. Run the following commands from a terminal window to set their permissions appropriately:

chmod 0701 ~
chmod 0701 ~/public_html
chmod 0604 ~/public_html/.htaccess
chmod 0701 ~/public_html/cgi-bin
chmod 0700 ~/public_html/cgi-bin/php-cgi

If you are still having problems, please email support@cs.jhu.edu for assistance.