Support

I would recommend AGAINST using that extension because it FORCIBLY caches the output of every page.

For starters, this would break the entire backend of your site unless you excluded /administrator from caching.

It will also cache all static media files, Joomla and third party extensions. This means that after each extension or Joomla update you MUST clear the LiteSpeed cache. Remember that extensions may store their static media files either in their own subdirectories or in a subdirectory of the media folder.

You will also have problem if you update static files in your template or even the images folder, e.g. overwriting an image with a new upload. You will need to manually clear the LiteSpeed cache.

As for Akeeba Backup, it will definitely break the Akeeba Backup JSON API and the frontend backup features since it will be caching the result of the API URLs instead of letting the server handle them. You will be told a backup is instantly finished without the backup ever running.

The LiteSpeed cache is great if you have a mostly static site which gets updated very irregularly. For anything else it will cause far more problems than it will solve.

Both issues you reported are already fixed.  A new version will be released today with those fixes.

Yes, excluding /administrator will cause no problems with Admin Tools.

Please note that as I said in my previous reply you will NOT be able to use Akeeba Backup's JSON API and frontend backup URL. Do not come and ask me to help you fix it. I can't. It's a server issue and you will have to ask your host how to fix it.

You're welcome!

If they ask you about the URL, it's /index.php?option=com_akeeba&view=api (v2 API) or /index.php?option=com_akeeba&view=json (v1 API) or /index.php?option=com_akeeba&view=backup (legacy backup). Caveat: there might be MORE query string parameters and they might be given in a different order then the one above. Moreover, if you are using SEF URLs it's possible that they are redirected to /component/akeeba?view=... by Joomla itself. The JSON API URLs may be accessed with a GET or a POST request. All of these factors are outside our control; they depend either on the third party service using the JSON API or Joomla itself. That's why whitelisting URLs cannot work for the JSON backup API and the legacy frontend backup URLs: we cannot give you a specific URL string.

Your host will need to figure out how to disable caching if the URL has the query string parameter option=com_akeeba (Joomla 3) or option=com_akeebabackup (Joomla 4) OR its path begins with /component/akeeba (Joomla 3) or /component/akeebabackup (Joomla 4).

Bon chance :) (I hope I didn't butcher this; I can read much more French than I can speak!)

No, I will not contact LiteSpeed developers again. I already told you that we are aware of the nature of the issue (LiteSpeed cache ignores the HTTP standard headers!) and they will not fix it. I told you that the only way for the JSON API to work is to either disable LiteSpeed cache or have your host create exceptions for certain URLs.

Please note that LiteSpeed Cache is SERVER SIDE CACHING. Your browser only reports client–side caching. The server side caching means that LiteSpeed will reply with a result it has cached on the server side WITHOUT running Joomla, WITHOUT our software running at all. Therefore the result will be wrong.

Since this is the third time I have explained the same thing in this ticket I will say this once more and close the ticket:

LiteSpeed Cache IS A BROKEN, BAD IMPLEMENTATION of server side caching. It can ONLY be used on sites which DO NOT CHANGE AT ALL. It cannot be used on sites which have any kind of dynamic elements such as but not limited to AJAX (XMLHttpRequest) calls to, per–user information such as login modules, JSON APIs etc. Using LIteSpeed Cache with dynamic elements will result in problems which are the sole responsibility of LiteSpeed Cache; the developers of the Joomla CMS and the third party extensions you are using objectively CANNOT help you.