Table of Contents

  • Introduction
  • Installation
  • Handling Challenger
  • Virtual Servers
  • Configuration Examples
    · Introduction
    · Standard Server
    · Secure server
    · User's Home Pages
    · FTP Server
    · Proxy Server
  • Modules
  • Filesystems
  • RXML Tags
  • Graphics
  • Proxy
  • Databases
  • Miscellaneous Modules
  • Security Considerations
  • Scripting
  • Frontpage
  • Upgrading
  • Third Party Extensions
  • Portability
  • Reporting Bugs
  • Appendix
  • Secure server
    Secure web server, using HTTPS to ensure noone can evesdrop on the communication. You must have one of the encrypted versions of Challenger, either the 40-bit version with weak encryption or the 128/168-bit version with strong encryption, to use HTTPS.

    1. Create a certificate.

      You need a certificate that ensures that your website really is your website. If you already have a certificate use this. Otherwize create one with the Security/Generate a RSA key and a self-signed certificate... action. This will produce two files, a certificate file as well as a RSA key file. The later file must be kept secret.

    2. Create a virtual server using the "Generic server" type.

    3. Configure the file system module.

      Filesystem
      Search path: Fill in the location, in the "normal" file system, where the HTML pages that should be used for the site will be located.

      Example: /usr/www/company_name/

    4. Configure the Server variables.

      • Configure a port.
        The default port for web servers using the HTTPS protocol is 443. You also have to fill in the location of your certificate file as well as the RSA key file. server.

    5. Click Save to save the server configuration on disk. The server will also try opening the port. You will be asked if the chosen URL for the site is correct. If you want to use another port than 80, you probably need to alter this.

      Note: Ports below 1024 can only be used if the server is run, or at least started, as root.

    Your server will not be secure until you get a certificate signed by a Certificate Authority like VeriSign or Thawte. In order to get a signed certificate you first produce a Certificate Signing Request through the Security/Generate a Certificate Signing Request for an RSA key... action.>