Hosting the static web files on a Domino HTTP server

About this task

This task only applies if you are hosting the Nomad for web browser static application files on a Domino HTTP server which SafeLinx references.


  1. Identify the directory inside the Domino data directory that will contain the static web files that Domino HTTP utilizes (for example, inside /domino/html as /nomad). This directory will be used for initial installations as well as all updates.
    Note: If the directory does not exist, create a new directory. The new directory needs to be under /domino/html, but the administrator can name that directory whatever they want.
    Note: If the directory already exists, backup the files (optional) and then delete all of the files including all the subdirectories.
  2. Unzip the static web files in the empty directory.
  3. Configure Domino HTTP to serve the HTTP files with the HTTP headers (see Hosting the Nomad for web browsers static web files).

    If you are using Internet Site Documents, the HTTP headers are specified via an HTTP response headers Web Site Rule. If you are not using Internet Site Documents, you may use the HTTPAdditionalRespHeader notes.ini.

    Note: For more information, see Creating a Web Site Rule document.
  4. Domino HTTP must specify the Content-Type for the .wasm files as application/wasm. Domino 11 and higher already includes this content-type definition, but earlier version of Domino will need this line added to the httpd.conf file:
    AddType  .wasm     application/wasm                     # WebAssembly


About this task

The configuration of SafeLinx to reference these Domino HTTP hosted files will be done later as part of SafeLinx configuration, but if HCL Nomad is already configured in SafeLinx, you need to update the SafeLinx configuration by completing the steps in VIA DOMINO HTTP SERVER in the topic Adding a Nomad server resource.