OpenLiteSpeed Settings
Configure global OpenLiteSpeed feature switches, security headers and TLS ciphers, then rebuild and verify affected virtual hosts.
Open Web Servers → OpenLiteSpeed → OpenLiteSpeed Settings.
Feature and header fields
All switches submit on or off. They control settings supplied to generated virtual hosts; enabling a switch does not install a missing module or service.
| Field | Purpose |
|---|---|
| ModSecurity 3 | Request filtering when the service is available. |
| LSCache | OpenLiteSpeed caching when available. |
| Directory Listing | Directory-index listing behavior. |
| Hotlink Protection | Hotlink restrictions generated by the template. |
| PageSpeed | PageSpeed behavior when supported. |
| HTTP Strict Transport Security | HSTS response-header setting. |
| Content Security Policy | Template-defined content-source policy. |
| XSS Protection | Legacy X-XSS-Protection header setting. |
| Clickjacking Protection | X-Frame-Options header setting. |
| Content-Type Protection | MIME-sniffing protection header setting. |
| Referrer Policy | Template-defined referrer policy. |
| Certificate Transparency | Legacy Expect-CT header setting. |
| Permissions Policy | Browser-feature policy switch, stored as the Feature-Policy setting. |
The switches select template behavior, not editable policy strings. Verify actual response headers and site compatibility rather than assuming a field label describes every browser's behavior.
Cipher list is required and accepts up to 2000 characters. The server form checks presence and length, not full compatibility with the installed TLS implementation.
Saved values and reset defaults
The page loads saved values. Its display fallbacks are not identical to every installed reset default, so review the actual values rather than assuming a fresh-looking form represents a reset.
The current reset helper enables LSCache, Directory Listing and Hotlink Protection. It disables the other switches and restores the supplied cipher expression.
Review exposure and compatibility
Directory listing can expose directory contents. HSTS and CSP can change browser behavior and break access or page resources when configured incompatibly. Review the generated policy and test HTTPS, framing and application resources before applying broadly.
Save and apply global defaults
- Record the current values.
- Change the intended fields and click Save Settings.
- Read the result.
- Use Rebuild Vhosts when the saved defaults need to be incorporated into generated virtual hosts.
- Confirm the rebuild, inspect taskd progress and logs, and verify affected sites.
- Use Restart only when the intended service operation is required.
Saving writes global preferences only. Existing domain overrides can continue to take precedence. The rebuild action starts the shared all-virtual-host task; it is not limited to a single selected domain. Its success message indicates task submission, not completion of all work.
Reset and service actions
Reset Defaults requires confirmation and writes the installed default settings. The current helper can return success even if writing fails; reload the page and verify saved values before proceeding. A reset does not itself rebuild every virtual host.
The button labeled Restart currently calls a service reload for OpenLiteSpeed and then queries service status. Do not assume a full stop/start occurred. Verify service and website behavior after the action.
Demo sessions cannot save, reset, rebuild or reload. On an I/O, validation or operating-system error, inspect the settings and logs before retrying.