LiteSpeed Cache for Flarum

rafaucau

qooba So you don't have this problem because you can see the changes. When the cache is served by LSCache then clearing the browser cache will not help. So it is only me who has this problem. So I am still looking for the cause

Darkle

rafaucau This is awesome! congratulations, thanks for releasing this as open source, I wish I could help with the development but unfortunately it's out of my capabilities.

A few months ago I was testing OLS, but finally I didn't switch as the performance of OLS compared to Nginx was exactly the same, this extension definitely makes the OLS+Flarum combination much more interesting, I hope to test it soon.

Gatsu

When I put the code in htaccess, I got internal 500 server error, why?
I use lite speed webserver

datlechin

Gatsu may be you put wrong place

can you show me your .htaccess file

Gatsu

datlechin Yes of course!

https://pastecode.io/s/xg1wk3hf

datlechin

remove line 169 -> 172 and paste this code to at the bottom

<IfModule LiteSpeed>
    CacheLookup on
    RewriteEngine On
    RewriteCond %{REQUEST_METHOD} ^HEAD|GET$
    # Detection of logged-in user.
    RewriteRule .* - [E="Cache-Vary:flarum_remember,flarum_lscache_vary"]
    # If you have a non-default path to the admin panel, change "admin" to match.
    RewriteCond %{ORG_REQ_URI} !/admin
    # Enable private cache for admin panel. If it causes problems replace "private" with "no-cache".
    RewriteRule .* - [E=Cache-Control:private]
</IfModule>

your code has not newlines

Gatsu

datlechin Thank you very much, now it works!

rafaucau

0.0.5

Add X-LiteSpeed-Vary header to response - Workaround for a strange problem where RewriteRule .* - [E="Cache-Vary:flarum_remember,flarum_lscache_vary"] is ignored. The problem only occurs on one account on our hosting, so it's probably rare.
Code cleanup

To do:

Another rare problem: on that hosting account there is a problem with automatic cache clearing when someone adds a post. This still makes it a bit impossible to use this extension with large TTL on our forum.

Darkle

rafaucau Another rare problem: on that hosting account there is a problem with automatic cache clearing when someone adds a post. This still makes it a bit impossible to use this extension with large TTL on our forum.

I don't know how rare it is, but I can confirm that I am also experiencing it.

rafaucau

Darkle I considered this a rare problem because no one has reported it and it works fine on the development site. On the production site it won't

Darkle

rafaucau Yeah, I was thinking of reporting it, I just wanted to do a few tests to make sure, by any chance what long TTL do you use? In my case it happens with 86400 (24 hours) I was thinking of trying shorter TTL, , I don't know if maybe it can influence something.

rafaucau

Darkle I am not currently using this extension due to a previous problem that today's update fixes. Tonight I will update it on production and set the TTL to two minutes. I would like the target TTL to be at least a week once I find the cause of the problem.
TTL does not affect the occurrence of the problem. It's more likely the LiteSpeed server configuration, but my hosting support could not find the cause yet.

xasharma

Loading composer repositories with package information
Updating dependencies
https://repo.packagist.org could not be fully loaded (Could not resolve host: repo.packagist.org), package information was loaded from the local cache and may be out of date
The following exception probably indicates you have misconfigured DNS resolver(s)

[Composer\Downloader\TransportException]
Could not resolve host: repo.packagist.org

update [--with WITH] [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-install] [--no-autoloader] [--no-scripts] [--no-suggest] [--no-progress] [-w|--with-dependencies] [-W|--with-all-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [-i|--interactive] [--root-reqs] [--] [<packages>]...

rafaucau

xasharma The following exception probably indicates you have misconfigured DNS resolver(s)

The problem is not with this extension. It's composer, packagist or your DNS

rafaucau

0.1.0

Add Serve Stale option android-com-pl/flarum-lscache8965165
You can learn more about this option here: https://docs.litespeedtech.com/lscache/lsclaravel/settings/#why-stale-purge-matters
Fix cleaning the cache when a new post is added android-com-pl/flarum-lscacheb486891
Cache CSRF API route android-com-pl/flarum-lscache32f63d1

0.1.1

Avoid unnecessary homepage cache cleaning

0.1.2

Fixed an issue where the discussion list API was not cleared after adding a new post

ash3T

rafaucau You need to include this code in your .htaccess file:

I am using Nginx, do you know what shall I add into the configure file?

rafaucau

ash3T This extension instructs the LiteSpeed server how to cache. It will not work on another server such as Nginx.
https://docs.litespeedtech.com/lscache/#what-is-lscache

ash3T

Got it. Thanks.

rafaucau

0.1.3

Clear homepage cache when a post is deleted / restored
Fixed an issue where the discussion list API cache was not cleared after adding a new discussion

rafaucau

0.1.4

Handle language switching @Darkle (android-com-pl/flarum-lscache1)

In the .htaccess replace:

RewriteRule .* - [E="Cache-Vary:flarum_remember,flarum_lscache_vary"]

to:

RewriteRule .* - [E="Cache-Vary:flarum_remember,flarum_lscache_vary,locale"]

« Previous Page Next Page »