This is an old revision of the document!


LSCWP Configuration Settings: Advanced

on

This option can be off if another cache plugin is used for non full page caching purposes. For example, the other plugin can be a db cache, minification, etc.

Note: If another cache plugin is not being used, it is recommended to leave this on.

empty string

This option should be used to configure a unique login cookie if multiple web applications with a LSCache plugin are used in a single virtual host.

An example login cookie is _wp_login_1

OFF

When a site uses both HTTP and HTTPS, conflicts with the login cookie may occur. Cookies are based on domain name, regardless of protocol, however an HTTP connection can't read a cookie that was saved with HTTPS. And so, if a user logs in with HTTPS and then connects with HTTP, the user will be treated as a guest, and not as a logged-in user.

When you enable this option, the login cookie is saved as an HTTP cookie at all times, regardless of the protocol used to access the page. This ensures that the login cookie is always accessible to both HTTP and HTTPS connections.

  • Admin
  • Last modified: 2017/12/19 14:39
  • by Lisa Clarke