From b65df4c602043d867a7cfe41c664b8e987a7f9a7 Mon Sep 17 00:00:00 2001
From: Adam Chlipala <adamc@hcoop.net>
Date: Tue, 9 Feb 2010 20:08:59 -0500
Subject: Tips for CGI scripts without httpd.conf access

---
 doc/manual.tex | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/manual.tex b/doc/manual.tex
index 3b6f05f1..1e5980ba 100644
--- a/doc/manual.tex
+++ b/doc/manual.tex
@@ -220,6 +220,19 @@ sqlite3 path/to/database/file <app.sql
 ScriptAlias /Hello /path/to/hello.exe
     \end{verbatim}
 
+    A different method can be used for, e.g., a shared host, where you can only configure Apache via \texttt{.htaccess} files.  Drop the generated executable into your web space and mark it as CGI somehow.  For instance, if the script ends in \texttt{.exe}, you might put this in \texttt{.htaccess} in the directory containing the script:
+    \begin{verbatim}
+Options +ExecCGI
+AddHandler cgi-script .exe
+    \end{verbatim}
+
+    Additionally, make sure that Ur/Web knows the proper URI prefix for your script.  For instance, if the script is accessed via \texttt{http://somewhere/dir/script.exe}, then include this line in your \texttt{.urp} file:
+    \begin{verbatim}
+prefix /dir/script.exe/
+    \end{verbatim}
+
+    To access the \texttt{foo} function in the \texttt{Bar} module, you would then hit \texttt{http://somewhere/dir/script.exe/Bar/foo}.
+
   \item \texttt{fastcgi}: This is a newer protocol inspired by CGI, wherein web servers can start and reuse persistent external processes to generate dynamic content.  Ur/Web doesn't implement the whole protocol, but Ur/Web's support has been tested to work with the \texttt{mod\_fastcgi}s of Apache and lighttpd.
 
     To configure a FastCGI program with Apache, one could combine the above \texttt{ScriptAlias} line with a line like this:
-- 
cgit v1.2.3