Search results

This was already posted before https://forum.openlitespeed.org/threads/how-to-reduce-image-headers-tips-on-faster-image-transfers.6147/post-16554, so there is nothing new, but the amount of data to be transfered if an image is requested can be reduced. As it is supported by OLS add this code to...

FYI: In this case css and js files are dynamically generated by PHP if these files do not exist yet, but the mime-type is respected if such files are generated. Ultimately, what counts is how PHP and witch PHP version is used to run the corresponding PHP Version for executing the script to...

Try disable Cloudflare cache and CF server timing in global CF configuration. Also change browser cache TTL setting to "Respect Existing Headers". FYI: CF APO is not compatible with LiteSpeed cache plugin for WordPress...

You shouldn't post a URL to a "secret" control panel. Just make a screenshot from response headers. Everybody can access to the control panel without login since all pages in control panel are cached by Cloudflare!

Do you like logic? I love logic (I am a fan of Spock and Data) and if you like solving problems using logic, then logic and previous knowledge should give you sufficient explanations. Ultimately, the issue can only be solved by identifying the responsible process. OLS and lsphp do not cause high...

You should realize that your server configuration may be sufficient for 2 WP sites, but not for 15. If you leave WordPress unchanged, i.e. no plugins and no special theme, your configuration may still be sufficient, but each plugin or theme increases the system requirements. This is especially...

@mkoylu The conditions for identifying the cause of the high load are not ideal. Modern content management systems (CMS) all use a PHP framework. This means that all PHP processes run via index.php. This makes it impossible to use system functions to identify individual processes that cause a...

Don't block if you don't know to what to block.....

Cache plugin support at WP forum is the one and only location where you get support for the LiteSpeed cache plugin, so please use it. Nevertheless, there is a nginx based proxy in front of your server and this proxy caches all requests and this constellation doesn't work with every other cache...

https://wordpress.org/support/topic/the-site-endlessly-makes-requests-to-itself-when-the-litespeed-wordpress-plugin/

You are using optimization features of the LiteSpeed cache plugin that require the LiteSpeed web server. Your 3rd party cache plugin is also incompatible with these optimization features.

Ask React or whatever, I don't know it......

However, there must be a CMS controlled function on your server that tricks the browser (Firefox) into expecting an incorrect mime type. This is not an OLS related issue!

No it isn't and I expect this answer. It seems you are using a CMS like WordPress or any other CMS. Many modern CMS catches all requests and also requests to whatever source type doesn't exists. That's why I asked you what is displayed if you request a source that doesn't exist AND if the...

And how do you identify that the mime type is not correct?

What is displayed if you request a URL that doesn't exist? The LiteSpeed default error page or a custom error page generated by any CMS?

You should still check if the relevant css files exist on your server. The Mime Type error is not a real Mime Type error in most cases, but first check if the css files exist and if the paths to the css files are correct. If either of these are not the case, then I will tell you why you are...

Is this WordPress related? If so, check the related css files if they exist.

If you have the Guestmode feature enabled, then the reload is caused by this feature, but it is not a bug. https://blog.litespeedtech.com/2021/06/01/guest-mode-for-wordpress-in-lscwp-v4-0/

This is not a PHP error, so there must be any other function (Plugin?) that controls it. This also means that changes to PHP configuration doesn't impact this error. For better error analysis, you should temporarily disable CF and enable WP debugging.