Support » Plugin: WP-Optimize - Cache, Clean, Compress. » Is this compatible with Litespeed?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Marc Lacroix

    (@marcusig)

    Hi there,

    Yes it should be compatible, as Litespeed is an Apache Drop-in Replacement.

    Marc.

    @totallyminimad I am successfully running it with OpenLiteSpeed on Ubuntu 18 with LSCache it detected LSCache and disabled its own cache but still works great at optimising the database on schedule.

    Just make sure that wp-cron can bypass the no abort check with a htaccess rule for example.

    <IfModule LiteSpeed>
    DisableCgiOverride On
    RewriteEngine On
    RewriteRule (wp-cron|backupsolution|someothersolution)\.php – [E=noabort:1, E=noconntimeout:1]
    </IfModule>

    Thread Starter totallyminimad

    (@totallyminimad)

    Hi.
    Thanks both.
    I am getting the following response so do i assume litespeed is working as well as WP Optize caching?

    https://drive.google.com/file/d/1Ho1UGZZ0YdbZMCYx7vfhdgQNgfYpyBxI/view?usp=sharing

    The cache headers show your using browser caching which is done by wp optimise. Personally I always opt for the built in server cache in litespeed and use wp optimise purely to keep my database lean.

    Plugin Support Marc Lacroix

    (@marcusig)

    @entrepreneuraj The browser caching complements the server cache, and is handled by the browser, not WP-Optimize. WP-Optimize enables you to add rules for browser caching for static assets only.

    The page cache functionality in WP-Optimize is a file-based cache, and can also often complement the server cache.

    @totallyminimad You won’t see proof of WP-Optimize page caching in the headers, but it adds a html comment at the bottom of the source code.

    Thread Starter totallyminimad

    (@totallyminimad)

    Thanks @entrepreneuraj and @marc Lacroix for your help.

    Will keep it running.

    Cheers
    minimad

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Is this compatible with Litespeed?’ is closed to new replies.