From c431b0649a983126cc350647953f44ac6cbe85b1 Mon Sep 17 00:00:00 2001
From: Claes Wikstrom
- Yaws supports plain CGI just fine. The two most common ways to run yaws cgi script is either as regular cgi scripts or as php scripts through the typical php-cgi binary. Yaws chooses how to ship a file pased on file extension. Let's start with the php-cgi example. PHP files have the extension .php and if we enable php by indicating it in yaws.conf:
+ Yaws supports plain CGI just fine. The two most common ways to run yaws cgi script is either as regular cgi scripts or as php scripts through the typical php-cgi binary. Yaws chooses how to ship a file based on file extension. Let's start with the php-cgi example. PHP files have the extension .php and if we enable php by indicating it in yaws.conf:
And then also ensure that we have enaable php processing for the individual server as in:
+ And then also ensure that we have enabled php processing for the individual server as in:
Plain CGI and PHP
-Yet another common scenario is when have a set of CGI files not ending with the \".cgi\" file extension. We can put all the CGI files in a common directory and define an appmod as follows: +Yet another common scenario is when have a set of CGI files not ending with the ".cgi" file extension. We can put all the CGI files in a common directory and define an appmod as follows:
@@ -91,7 +91,7 @@ and then configure the appmod appropriately in yaws.conf. The default yaws.conf-Thus if we put put any executable files in the \"cgi-bin\" directory under the docroot, Yaws will speak CGI to those executables. +Thus if we put put any executable files in the "cgi-bin" directory under the docroot, Yaws will speak CGI to those executables.