LiteSpeed Cache for WordPress Settings: Cache

on

This setting allows content to be cached for logged-in users. Pages will be stored in private cache by IP/session ID.

on

This option is useful for the WordPress option that requires moderation on guest comments. If that option is set, this option will serve the cached version of the page, meaning the commenters will not see their under moderation comments. If off, commenters will not be served from cache.

on

This option allows you to cache requests that are made by WordPress REST API calls.

on

This option will cache the login page. Normally, there is no reason to uncheck this option. However, if there is something that may identify a user on the page, this should be off.

on

This option will cache the favicon.ico response if it does not exist. The reason for caching this is because if the file does not exist, it will load WordPress every time. This will avoid that extra call.

on

This option will cache any PHP resources loaded by themes. Generally speaking, these are css or js resources loaded in PHP. In most cases, these are static outputs, so there is no reason to load PHP every time. If they are in fact dynamic, this should be off.

off

This option enables users to display a separate html for mobile and desktop views. This is primarily used for non-responsive themes, but can also be used in situations where different widgets are loaded depending on browser type.

The list of Mobile View User Agents must not be empty when this is on.

disabled/string

If Cache Mobile is set to off, this text box will be grayed-out. Once enabled, this list should be filled in with a rewrite-rule-friendly list of user agents.

SYNTAX: Each entry should be separated with a bar, '|'. Any spaces should be escaped with a backslash before the space, '\ '. The default list WordPress uses is Mobile|Android|Silk/|Kindle|BlackBerry|Opera\ Mini|Opera\ Mobi

empty string

A list of path patterns that should never be publicly-cached. To make an exact match, add a $ to the end. One per line.

Examples:

  • private matches category/private, category/private-posts, tag/private, and 2017/10/i-took-a-private-phone-call.
  • /category/private matches /category/private and /category/private-posts.
  • /category/private$ matches only /category/private.

These settings have moved to the Advanced tab.

These settings have moved to the Advanced tab.

empty string

This setting allows you to specify the query strings that should be ignored by LSCache.

Some query strings, particularly those that are used for marketing or analytics purposes, have no effect on the content that is displayed on the page. The page renders the same with and without these query strings. As such, it should not be necessary to store multiple copies of the page in the cache. Learn more.

  • Admin
  • Last modified: 2019/04/12 18:32
  • by Lisa Clarke