[Zope-Checkins] CVS: Zope/doc - WEBSERVER.txt:1.21.2.1

[Fred L. Drake, Jr.]

Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv2491

Modified Files:
      Tag: new-install-branch
	WEBSERVER.txt 
Log Message:
- update some of the PCGI-related instructions
- wrap some long lines


=== Zope/doc/WEBSERVER.txt 1.21 => 1.21.2.1 ===
--- Zope/doc/WEBSERVER.txt:1.21	Wed Mar  5 14:05:56 2003
+++ Zope/doc/WEBSERVER.txt	Wed Mar  5 14:17:00 2003
@@ -45,24 +45,23 @@
 
  PCGI
 
-  To install PCGI, please read the pcgi/README file.
+  To install PCGI, please get the PCGI support package from XXX, and
+  read the pcgi/README.txt file from that package.
 
-  To run ZServer with PCGI, you must specify the -p option to the
-  'z2.py' startup script.  From the top level Zope directory, you
-  can::
-
-    bash% python2.2 z2.py -p
+  To run ZServer with PCGI, you must configure Zope with a PCGI
+  server.  You can do this by adding a section to the etc/zope.conf
+  file like this::
+
+    <pcgi-server>
+      address /path/to/PCGI/resource/file
+    </pcgi-server>
 
   Note, you must have gone through the directions in 'INSTALL.txt' for
   this to work.
 
-  This command will start ZServer up with PCGI (by default, it will
-  also start up an HTTP and FTP server).  For PCGI to work, the
-  webserver and Zope must agree on a PCGI resource file.  If this file
-  is not named 'Zope.cgi' and is not in the same directory as 'z2.py',
-  then you can specify the file name after the '-p', like::
-
-    bash% python2.2 z2.py -p /path/to/PCGI/resource/file
+  This command will cause Zope to start with a PCGI server as well as
+  any other servers you specify in the zope.conf file.  For PCGI to
+  work, the webserver and Zope must agree on a PCGI resource file.
 
   Now the Zope long running process is started up, and the PCGI
   component is loaded and ready to receive CGI requests from your
@@ -431,33 +430,35 @@
 
       * An ISAPI module to support PCGI is under development.
 
-      * IIS 4.0 throws away Zope's error messages by default. This 
-        behavior can create quite a few problems, including authentication 
-        problems.
-
-      Microsoft prides itself on the clear error messages that IIS 4.0 
-      presents, when the user makes a mistake. These error messages are 
-      implemented in the form of Custom Error handlers, that return a file, 
-      or URL to a user when a certain error occurs.
-
-      This means, that when you forget to fill in an Id when you want to 
-      create, say, a new SQL Method, Zope's clear error message is replaced 
-      by IIS's totally irrelevant error message. Also, it completely breaks 
-      authentication when the user uses IE5.0 when trying to log into a secure 
-      area of the server. These Custom Error handlers are enabled by default.
+      * IIS 4.0 throws away Zope's error messages by default. This
+        behavior can create quite a few problems, including
+        authentication problems.
+
+      Microsoft prides itself on the clear error messages that IIS 4.0
+      presents, when the user makes a mistake. These error messages
+      are implemented in the form of Custom Error handlers, that
+      return a file, or URL to a user when a certain error occurs.
+
+      This means, that when you forget to fill in an Id when you want
+      to create, say, a new SQL Method, Zope's clear error message is
+      replaced by IIS's totally irrelevant error message. Also, it
+      completely breaks authentication when the user uses IE5.0 when
+      trying to log into a secure area of the server. These Custom
+      Error handlers are enabled by default.
 
       Luckily, the handlers can quite easily be switched off:
 
-      Open the IIS website in the Management Console, and navigate to the 
-      folder you put the PCGI executable in. If you named your Zope installation 
-      'Zope', it will be called 'Zope.exe'. Double-click on that file. A property 
-      page will appear. Select the 'Custom Errors' tab. Now, select every HTTP 
-      Error code in the listbox that doesn't have type 'Default', and click on 
-      the 'Set to Default' button for each one. This will disable IIS overriding 
-      the error message returned by Zope.
+      Open the IIS website in the Management Console, and navigate to
+      the folder you put the PCGI executable in. If you named your
+      Zope installation 'Zope', it will be called
+      'Zope.exe'. Double-click on that file. A property page will
+      appear. Select the 'Custom Errors' tab. Now, select every HTTP
+      Error code in the listbox that doesn't have type 'Default', and
+      click on the 'Set to Default' button for each one. This will
+      disable IIS overriding the error message returned by Zope.
 
-      Click OK, and voila, Zope is allowed to tell the world what it thinks went
-      wrong.
+      Click OK, and voila, Zope is allowed to tell the world what it
+      thinks went wrong.