Search results

You mean more responsive, not responsible..... :)

You better should contact vBulletin support (forum). Rendering issues is not a LSWS issue and is responsible by vBulletin

In WebAdmin check PHP Handler Defaults > Max Connections in PHP Tab. For 8 core CPU setting should be ~ 35 - 40. Maybe it helps....

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

Cache header will automatically be set if LSCache is used. No Cache - No Header - No Header - No Cache. You need either a cache plugin or at least .htaccess rewrite rules to enable LSCache.

Pagespeed Insight doesn't measure the page load time. It measures the time how long it takes to display after all data has been transfered to the client. That is something complete different as the page load time. If you want to check you server speed you must use other analyze tools but not...

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,*');