Differences
This shows you the differences between two versions of the page.
litespeed_wiki:cache:auto-fix-cache-files-directories-permission [2018/08/20 18:19] Jackson Zhang created |
litespeed_wiki:cache:auto-fix-cache-files-directories-permission [2018/08/20 20:05] (current) Lisa Clarke Proofreading |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Improved cache engine to fix bad cache storage directory and file permissions ====== | + | ====== Fix Bad Cache Storage Configuration ====== |
- | Normally for control panel environment, server level and virtual host level cache root are set in apache configuration(or include files). Once they are set and restart LSWS, web server will create such directory automatically with correct ownership and permissions. | + | LiteSpeed Web Server, as of v5.3, has an improved cache engine that can fix badly-configured cache storage directories and file permissions. |
- | However, some user may have manually created such cache folder with wrong ownership or permission, which will later cause a lot of problems such as cache creation or cache lookup etc. | + | Normally in a control panel environment, server-level and virtual-host-level cache roots are set in the Apache configuration, or in include files. Once these are set and LSWS is restarted, the web server will create the required directories automatically, and with correct ownership and permissions. |
- | LSWS 5.3 introduced a feature to automatically fix such cache root directory and permission problem. | + | However, a user may have manually created a cache folder with the wrong ownership or permissions. This will cause a lot of problems later when creating cache entries of looking them up. LSWS 5.3+ addresses this problem by automatically fixing such cache root issues. |
- | ===== Auto fix cache directory and file permissions ===== | + | ===== Example: Cache Directory and File Permissions ===== |
- | For example, on cpanel, usually a virtual host level cache root is normally set to /home/$USER/lscache with "nobody:user" ownership. | + | For example, on cPanel, usually a virtual-host-level cache root is normally set to ''/home/$USER/lscache'' with ''nobody:user'' ownership. |
- | Somehow the user may manually create /home/$USER/lscache with "user:user" ownership. When restarting LSWS 5.3, server will automatically detect such error and change the cache diretory to be owned by "nobody:user". | + | If, somehow, a user has manually created ''/home/$USER/lscache'' with ''user:user'' ownership, when LSWS restarts, the server will automatically detect the error and change the cache diretory to be owned by "nobody:user". |
- | ===== Create directory during the first access When "JIT" enable ===== | + | ===== Example: Create Directory ===== |
- | Let 's give another example. | + | Previously, when [[https://www.litespeedtech.com/docs/webserver/config/general#jitConfig|Just In Time Configuration]] was enabled on the LSWS server configuration, a virtual host cache folder could not be created. The way to fix it was to disable JIT in virtual host configuration. |
- | For LSWS 5.2.x and lower version, when [[https://www.litespeedtech.com/docs/webserver/config/general#jitConfig|Just In Time Configuration]] is enabled on LSWS server configuration, seems virtual host cache folder cannot be created. The fix to it is to disable "JIT" in configuration. | + | Now, LSWS 5.3 and later can handle such a situation. Even when "Just In Time Configuration" is enabled, after the first request hits the vhost, ''lscache'' will be created. For this case, cache won't be used for the first request and there will be a little delay for vhost to enable cache. This is by design. |
- | + | ||
- | LSWS 5.3 can handle such a situation. Even when "Just In Time Configuration" is enabled, after the first request hitting the vhost, **"lscache"** will be created. For this case, cache won't be used for the first request and there is little delay for vhost to enable cache, as designed. | + |