Mercurial > urweb
changeset 1753:957168662198
Clarify need for 'prefix' for FastCGI
author | Adam Chlipala <adam@chlipala.net> |
---|---|
date | Sun, 06 May 2012 15:34:10 -0400 |
parents | 675ce534e3ec |
children | a1380fc15cb5 |
files | doc/manual.tex |
diffstat | 1 files changed, 3 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/manual.tex Sun May 06 15:27:30 2012 -0400 +++ b/doc/manual.tex Sun May 06 15:34:10 2012 -0400 @@ -265,7 +265,7 @@ \item \texttt{-prefix PREFIX}: Equivalent to the \texttt{prefix} directive from \texttt{.urp} files -\item \texttt{-protocol [http|cgi|fastcgi]}: Set the protocol that the generated application speaks. +\item \texttt{-protocol [http|cgi|fastcgi|static]}: Set the protocol that the generated application speaks. \begin{itemize} \item \texttt{http}: This is the default. It is for building standalone web servers that can be accessed by web browsers directly. @@ -299,6 +299,8 @@ \end{verbatim} The idle timeout is only important for applications that use message-passing. Client connections may go long periods without receiving messages, and Apache tries to be helpful and garbage collect them in such cases. To prevent that behavior, we specify how long a connection must be idle to be collected. + Also see the discussion of the \cd{prefix} directive for CGI above; similar configuration is likely to be necessary for FastCGI. An Ur/Web application won't generally run correctly if it doesn't have a unique URI prefix assigned to it and configured with \cd{prefix}. + Here is some lighttpd configuration for the same application. \begin{verbatim} fastcgi.server = (