Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:cache:lscwp:configuration:advanced [2018/01/29 21:05] Lisa Clarke [Improve HTTP/HTTPS Compatibility] Added Instant Click |
litespeed_wiki:cache:lscwp:configuration:advanced [2020/11/14 15:22] (current) Lisa Clarke Redirect to new Documentation Site |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== LSCWP Configuration Settings: Advanced ====== | + | ~~REDIRECT>https://docs.litespeedtech.com/lscache/lscwp/toolbox/~~ |
| - | + | ||
| - | {{:litespeed_wiki:cache:lscwp:lscwp-settings-advanced.png?direct&800|}} | + | |
| - | + | ||
| - | ===== Check advanced-cache.php ===== | + | |
| - | //on// | + | |
| - | + | ||
| - | This option can be off if [[litespeed_wiki:cache:lscwp:customizations:multi-cache-plugins|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. | + | |
| - | + | ||
| - | ===== Login Cookie ===== | + | |
| - | //empty string// | + | |
| - | + | ||
| - | This option should be used to configure a unique login cookie if [[litespeed_wiki:cache:multi-app|multiple web applications]] with a LSCache plugin are used in a single virtual host. | + | |
| - | + | ||
| - | An example login cookie is _wp_login_1 | + | |
| - | + | ||
| - | ===== Improve HTTP/HTTPS Compatibility ===== | + | |
| - | //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. | + | |
| - | + | ||
| - | ===== Instant Click ===== | + | |
| - | //OFF// | + | |
| - | + | ||
| - | It takes time for a user to click a link. First they hover over it, then they depress the mouse button, and //then//, only after the button is released, is the link considered "clicked" and the new page loaded. With Instant Click enabled, the page begins to load as soon as the user hovers over the link. By the time the mouse button is released, enough of the page has been loaded that the display can seem almost instant. | + | |
| - | + | ||
| - | Be aware, though, that this function will generate extra requests to the server, if your visitors do a lot of link hovering without clicking. As such, it has the potential to impact server load. | + | |
| - | + | ||