Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Date: Thu Apr 5 08:02:05 2007
New Revision: 6399
Added side note concerning custom error pages.
--- Webware/trunk/WebKit/Docs/Configuration.txt (original)
+++ Webware/trunk/WebKit/Docs/Configuration.txt Thu Apr 5 08:02:05 2007
@@ -288,7 +288,7 @@
You can use this to set up custom error pages for HTTP errors and any
- other exceptions raised in Webware servlets. Set it to the URL of a
+ other exceptions raised in Webware servlets. Set it to the URL of a
custom error page (any Webware servlet) to catch all kinds of exceptions.
If you want to catch only particular errors, you can set it to a dictionary
mapping the names of the corresponding exception classes to the URL to
@@ -310,10 +310,13 @@
will be automatically forwarded to the corresponding error page servlet.
More specifically defined exceptions overrule the more generally defined.
You can even forward from one error page to another error page unless
- you are not creating loops. In an ``HTTPNotFound`` error page, the servlet
+ you are not creating loops. In an ``HTTPNotFound`` error page, the servlet
needs to determine the erroneous URI with ``self.request().previousURI()``,
since the ``uri()`` method returns the URI of the current servlet, which
- in the error page itself. Default: ``None`` (no custom error page).
+ in the error page itself. When a custom error page is displayed, the
+ standard error handler will not be called. So if you want to generate
+ an error email or saved error report, you must do so explicitly in your
+ error page servlet. Default: ``None`` (no custom error page).
Values in exception reports are truncated to this length, to avoid
excessively long exception reports. Set this to ``None`` if you