Skip to Content
Browse documentation

Edit OpenLiteSpeed Domain Settings

Set per-domain OpenLiteSpeed overrides, choose an application template and understand exactly what Reset Defaults removes.

From OpenLiteSpeed Domains, open a domain's editor.

How values are loaded

The editor starts with global OpenLiteSpeed settings and overlays any saved domain settings. A non-default application selection is shown as the selected template. Review the displayed domain and owner before saving.

Domain profile

FieldRequirement
Application TemplateRequired template selection, maximum 200 characters in the form.
OpenLiteSpeed UserDirOn/off; enables Apache-style user-directory access for the domain.

The application selector is populated from supplied, global custom and account template locations. Availability in the selector is not a complete compatibility test. Changing it updates the domain's application selection, which is shared domain metadata.

Feature, header and TLS fields

The editor includes the same 13 feature/header switches and required Cipher list described in OpenLiteSpeed Settings: ModSecurity 3, LSCache, Directory Listing, Hotlink Protection, PageSpeed, HSTS, CSP, XSS Protection, Clickjacking Protection, Content-Type Protection, Referrer Policy, Certificate Transparency and Permissions Policy.

Every switch must submit on/off. The cipher string is limited to 2000 characters. The form does not fully validate the generated policy or TLS expression.

Save domain settings

  1. Record current values and the application selection.
  2. Choose the template and UserDir status.
  3. Review all feature/header switches and the cipher list.
  4. Click Save Domain Settings.
  5. Read the result and verify the generated virtual host and site.

Saving stores the displayed OpenLiteSpeed values as explicit domain settings, updates the application and UserDir values, and invokes the shared domain builder. It does not merely save the fields you touched. Subsequent global changes may therefore be masked by these domain overrides.

The success result follows the metadata write and does not independently prove every build/reload step completed.

Review alternate access and policy changes

UserDir can expose content through an additional URL. Template and security-header changes can affect routing, application resources and browser behavior. Verify the intended access paths after saving.

Reset Defaults

Click Reset Defaults, inspect the domain in the confirmation and confirm.

The current reset removes the domain's OpenLiteSpeed override block and sets its application to default, then invokes the domain builder. It does not reset the separate UserDir value. The editor then displays the applicable global defaults.

Record the prior application and overrides before resetting. Resetting is not a rollback to the immediately previous save. Demo sessions cannot save or reset.