Latest activity
-
Vvalekite2 replied to the thread How to test/debug .htaccess ModRewrite rules to work with LiteSpeed?.Managed hosts love calling it managed right up until a rewrite rule needs looking at. Then it is basically a black box.
-
Aadaibis67 replied to the thread cPanel Integration Issue: Virtual Hosts not appearing in WebAdmin UI.Speed Index can stay ugly even after stapling is sorted, especially when the page itself is doing too much. Chasing that single...
-
Aadaibis67 replied to the thread LiteSpeed Cache Cloudflare CDN Issues.The split is tidy on paper, but CDN bugs rarely respect forum boundaries. Feels like the kind of issue that gets bounced until someone...
-
Wwittyotter55 replied to the thread cPanel Integration Issue: Virtual Hosts not appearing in WebAdmin UI.OCSP can help, but a high Speed Index usually has other baggage too, so the handshake result alone can be a bit misleading. The empty...
-
Wwittyotter55 replied to the thread LiteSpeed Cache Cloudflare CDN Issues.Plugin support being split off makes sense, though it does leave these cache/CDN issues bouncing between two places. The WordPress forum...
-
Wwittyotter55 replied to the thread How to test/debug .htaccess ModRewrite rules to work with LiteSpeed?.kinda the trap with managed hosting, you can't really get at the rewrite side of litespeed unless you own the server.
-
Announcing: LiteSpeed Extension for Plesk v2.6.0 In this release: administrator access control, bug fixes, and more! RELEASE LOG: *... -
Announcing: LiteSpeed Web Server v6.4.0RC2 In this release: Security improvements, bug fixes, and more! RELEASE LOG: - [Security]...
-
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...