Sets the size of the internal page cache, where size is the number of byte-compiled pages to be cached for future use. Default is MaxRequestsPerChild / 5, or 50, if MaxRequestsPerChild is 0.

This option is completely global, even when using separate, per-virtual host interpreters.

Tcl script that is run when each interpreter is initialized. script is an actual Tcl script, so to run a file, you would do:

RivetServerConf GlobalInitScript "source /var/www/foobar.tcl"

This option is ignored in virtual hosts.

Script to be evaluated when each Apache child process is initialized. This is the recommended place to load modules, create global variables, open connections to other facilities (such as databases) and so on.

In virtual hosts, this script is run in addition to any global childinitscript.

Script to be evaluated when each Apache child process exits. This is the logical place to clean up resources created in ChildInitScript, if necessary.

In virtual hosts, this script is run in addition to any global childexitscript.

Script to be evaluated before each server parsed (.rvt) page. This can be used to create a standard header, for instance. It could also be used to load code that you need for every page, if you don't want to put it in a GlobalInitScript ChildInitScript when you are first developing a web site.

In virtual hosts, this option takes precedence over the global setting.

Script to be called after each server parsed (.rvt) page.

In virtual hosts, this option takes precedence over the global setting.

When Rivet encounters an error in a script, it constructs an HTML page with some information about the error, and the script that was being evaluated. If an ErrorScript is specified, it is possible to create custom error pages. This may be useful if you want to make sure that users never view your source code.

In virtual hosts, this option takes precedence over the global setting.

AfterEveryScript is a script that is to be run anyway before requests processing ends. This script is therefore run both when the content generation script completes successfully and when its execution is interrupted by abort_page. The code in this script can tell whether we are running after an abort condition occurred by passing the argument ?-aborting? to abort_page which in turn returns 1 if abort_page had been called earlier in the request processing.

Execution of a content generating script can be done by invoking abort_page. When an AbortScript is defined for the page being generated, control is passed to it as a way to undertake specific action that might be necessary to catch resources left dangling by the sudden interruption.

Directory to place uploaded files.

In virtual hosts, this option takes precedence over the global setting.

Maximum size for uploaded files.

In virtual hosts, this option takes precedence over the global setting.

This option controls whether it is possible to upload files to a Tcl variable. If you have a size limit, and don't have to deal with large files, this might be more convenient than sending the data to a file on disk.

If on, Rivet will create a separate Tcl interpreter for each Apache virtual host. This is useful in an ISP type situation where it is desirable to separate clients into separate interpreters, so that they don't accidentally interfere with one another.

This option is, by nature, only available at the global level.

If a HEAD requests is issued by the client Rivet detects this case and sends back to the client a standard header response. If the real header has to be examined (e.g. for debugging) you can turn this options on.

This option is, by nature, only available at the global level