Search results

Remove everything from Google and you will get a much better score. This is not a LSWS issue!

For your information: OLS has some restrictions in comparison to LSWS Enterprise. A restriction can be a delay when cache will be purged. This seems to be undocumented. Another user of OLS reported this and got this information from his hosting provider. Maybe this could cause your issue

1.) To purge cache by tag page must be cached with tag first. If cache is purged you must see tag name in response header. 2.) Replace this header with a test header like: return response()->json('', 200, [ 'Testheader' => 'test']); and check response header if you request login page. If test...

Have you excluded login/logout/register/signin from being cached?

Now it is proofed and it works. That means your code is wrong. You better should contact Laravel support to get help.

Says who? You or staff from OLS? You can verify it. Create an empty PHP file and execute it with header: header('X-LiteSpeed-Purge:stale,*');

Dann sag denen mal einen schönen Gruß, dass ich deren LiteSpeed Angebot demnächst mal etwas erweitern möchte. :)

Have you already tried to purge cache by URL? Same syntax but with URL instead: header('X-LiteSpeed-Purge: /aktivitaeten/fritigs-maetschli'); If this also doesn't work something is wrong how you set header in Guzzle. Btw. Where do your host your page in Switzerland?

@Max38 For your information only: OLS has an own support forum: https://forum.openlitespeed.org/ This forum is for LSWS Enterprise customers.

@Solaris Maybe I missunderstand what your problem is, but before a cached page can be purged by using cache tag a page must be cached with this tag. If your code is correct you must see cache tag in response header if you request the non cached page. And ofcourse you can't set a response...

Check this: https://docs.litespeedtech.com/lscache/lsclaravel/settings/#purge

To provide you with support would you please provide us first with specific information what should happen when whatever happens?

Sorry, I couldn't know complete context of code and the method how to set header in Laravel. If cache will not be cached maybe you set header to late. You must set the header before POST request is finished. Example: if (isset($_POST['action']) && ($_POST['action'] == 'whatever')) {...

Syntax is wrong header('X-LiteSpeed-Purge:stale,*');

This is not a cache problem, but a problem of wrong plugin settings for optimizing. Your css is loaded by javascript and javascript is loaded defered. That's why you see an unformated layout after page loading. Purging CDN cache could help, but to solve it you better should visit home of LScache...

Google is your friend: :) https://www.google.com/search?q=change+ssh+port+centos

@sibipaul Thank you for your explanation, but there is a much easier way to protect unallowed SSH access. First of all and the most important to do: Change SSH standard port. This reduces the rate of login tries up to 90%. If you have cPanel, use cPHulk and ConfigServer Security & Firewall...

If it is just a regular expires header, why do you name it a new "feature"? Setting expires header to a partial response could already be done before v5.4.9 with Apache rewrite rules?!

Disable adblocker in your browser...... This is not a LSWS issue!

LiteSpeed Web Server v5.4.9 Build 1 has been released yesterday. This build has a new feature to apply expires header to a partial response for a range request. Where can I find more information to apply this new feature?