Latest activity
-
serpent_driver replied to the thread How to test/debug .htaccess ModRewrite rules to work with LiteSpeed?.If you are the license owner for LSWS, login to LiteSpeed user panel and ask for support. Otherwise or if you are not the server admin... -
Announcing: LiteSpeed Web Server v6.3.7 In this release: Security improvements, bug fixes, and more! RELEASE LOG: [Security] Enhance... -
serpent_driver replied to the thread Wordfence for WordPress expands LiteSpeed's noabort exception site-wide because its own architecture cannot isolate the requests that need it.Thanks for the clarification. Since LiteSpeed understandably does not want to judge the architecture or configuration recommendations of...
-
EErnestSimpson replied to the thread Wordfence for WordPress expands LiteSpeed's noabort exception site-wide because its own architecture cannot isolate the requests that need it.The practical answer is: noabort is not generally meant to be a blanket, site-wide switch. Our guidance remains that it should be scoped...
-
Announcing: LSCache for WordPress v7.9.1 In this release: Image Optimization improvements, bug fixes, and more! RELEASE LOG: - Core...
-
TateDoyle replied to the thread Wordfence for WordPress expands LiteSpeed's noabort exception site-wide because its own architecture cannot isolate the requests that need it.I think the distinction you are making here is the important one. There is nothing inherently wrong with Wordfence needing noabort for... -
abk replied to the thread Wordfence for WordPress expands LiteSpeed's noabort exception site-wide because its own architecture cannot isolate the requests that need it.Thanks for the follow-up. As noted above, our documentation covers the technical guidance on scoping noabort, and how it's applied on a... -
serpent_driver replied to the thread Wordfence for WordPress expands LiteSpeed's noabort exception site-wide because its own architecture cannot isolate the requests that need it.Thanks, and I agree with your answer. I am not asking LiteSpeed to decide how another administrator should configure their server. Your...
-
abk replied to the thread Wordfence for WordPress expands LiteSpeed's noabort exception site-wide because its own architecture cannot isolate the requests that need it.All I can respond to this is what our documentation already answers: noabort should normally be scoped to the specific script or URL...
-
serpent_driver posted the thread Wordfence for WordPress expands LiteSpeed's noabort exception site-wide because its own architecture cannot isolate the requests that need it in General Support.This post is based on an discussion on Reddit: You should read the comments to better understand what this post is about: I recently...
-
-
abk replied to the thread LiteSpeed Cache breaks REST API auth (WP Vibe) and Matomo internal request routing — reproducible, confirmed via clean preset baseline.Please use the WordPress forum for our WordPress plugin questions/issues...
-
IndeMoJo posted the thread LiteSpeed Cache breaks REST API auth (WP Vibe) and Matomo internal request routing — reproducible, confirmed via clean preset baseline in Bug Reports.LiteSpeed Cache breaks REST API auth (WP Vibe) and Matomo internal request routing — reproducible, confirmed via clean preset baseline... -
abk replied to the thread Rendering issues.Please use the WordPress forum for our WordPress plugin questions/issues...
-
RMy site is not rendering properly (see screenshot) for a number of browsers. I disabled LiteSpeed cache and formattig returned to...
-
-
abk replied to the thread Lite Speed is slowing down wordpress admin parts.Please use the WordPress forum for our WordPress plugin questions/issues...
