Search results

I can't give you any specific information about LAravel because I have no experience with Laravel, but the basic principle of LScache is the same for all CMS. Excluding POST requests from caching is obsolete because POST requests are not cached by default. From your code shown there is no...

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

Which CMS and cache plugin are you talking about? There are more than 1 CMS and for each CMS there is a different cache plugin!

You have already opened a thread in the Wordpress Support Forum for the LiteSpeed Cache Plugin. There and only there you will get support for the cache plugin because this forum no longer offers support for the cache plugin...

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

Which CMS and cache plugin do you use?

Yes, really.

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

What you expect works, if the location of 403.shtml is correct. cPanel expects 403.shtml in document_root while document_root is the location/path where the domain points to. Any other location doesn't work and is not respected. Ofcourse it matters, so why to define a rewrite rule to protect...

Since the user @continet doesn't give an answer to my last question, but perhaps other users want to know the answer to my last question, here is the answer. Directories that are not within the publicly accessible area do not need to be specifically protected from access, simply because they...

Do you try to block access to cpanel location for passwords?

Please describe (exactly) what should be displayed if someone requests a source he isn't allowed to access.

As is often the case, you don't know what you're talking about. Please do us all a favor and don't talk about topics you don't have any knowledge about. Also, I'm not talking about your incorrect wording, but about the wording of the description in the cache plugin.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403 https://en.wikipedia.org/wiki/HTTP_403 https://httpd.apache.org/docs/2.4/rewrite/flags.html Using the [F] flag causes the server to return a 403 Forbidden status code to the client. While the same behavior can be accomplished using...

This is a wrong wording. Memcached and Redis are not enabled at the same time. "enabled" means that both object caches are available, but not enabled. If Memcached or Redis is "available", then there is no need to install additonal object cache. Settings for Memcached or Redis are just not...

You can set your own 403.shtml. .shtml is just html and can be styled and filled with every content, but you must follow 403 restrictions. You can't deny access to whatever source and allow access to sources at the same time. cPanel follows Apache directive for errorDocument. If you don't like...

Yes, I removed LiteSpeed label in this (my) 403.shtml. What else are you complaining about now?

Search for memcached.sock on your server and use this code to test if Memcached works. $mc = new Memcached(); $mc->addServer('/path_to/memcached.sock', 0) or die ("Unable to connect"); echo "Server version:<pre>"; print_r($mc->getVersion()); echo "</pre>"; $tmp = new stdClass; $tmp->str_attr...

Of course you see the same content because the 403.shtml is the LiteSpeed 403.shtml page. You can change the 403.shtml as you wish, but it must always remain the 403.shtml file and you are not allowed to include any static elements in it.

If you use cPanel, then you are not allowed to define an error_document for 403, because 403 means that access to any source is prohibited and therefore also to a custom error_document. That sounds paradoxical, but it is true. The cPanel configuration expects a 403.shtml in the document_root...