Table of Contents
- Introduction
- Installation
- Handling Challenger
- Virtual Servers
- Configuration Examples
- Modules
- Filesystems
- RXML Tags

  | · Introduction · Main RXML parser · RXML Packages · Countdown · Flik · Indirect Href · Obox · Pike Tag · SED · Tablify · Wizard

- Graphics
- Proxy
- Databases
- Miscellaneous Modules
- Security Considerations
- Scripting
- Frontpage
- Upgrading
- Third Party Extensions
- Portability
- Reporting Bugs
- Appendix

Main RXML parser
This module must be installed if you want your Roxen to parse any RXML tags. It does contain the actual RXML parser as well as some RXML tags. Other modules may supply more RXML tags.

This module is a file extension module, you choose the extensions of the files to be parsed. For some sites that may be any `.html` or `.htm` file. Other sites may want to limit parsing to special files, maybe `.rxml` files.

`Access log`
  This variable controls whether to enable the `<accessed>`. The `<accessed>` tag uses two files, `logs/<virtual server name>/Accessed.db` and `Accessed.names` to store how many times a page has been visited. Since the tag takes more resource than most others it can be disabled.

`Extensions to accesscount`
  By default the `<accessed>` tag only counts accesses to pages that contain the `<accessed>` tag itself. This means that all pages you put an `<accessed>` on will start counting from zero.

  This option makes it possible to specify a few file extensions, access files ending with these extensions will always be counted. Thus it will be possible to count accesses to all `.html` files. This access counting will take a significant amount of resources.

`Extensions to parse`
  File endings that show which file extensions should be run through the RXML parser.

`SSI support...`
  `NSCA and Apache SSI support`
    If set, Roxen will parse NCSA / Apache server side includes.

  `execute command`
    If set and if server side include support is enabled, Roxen will accept NCSA / Apache exec commands, `<--#exec cmd=command-->`. This has security implications, refer to the SSI page for more information.

  `execute command gid`
    The group id of processes started by SSI exec commands.

  `execute command uid`
    The user id of processes started by SSI exec commands.