Today we are configuring browser caching control on common Apache 2 servers. Caching is a great tool to reduce server resource consumption, bandwidth utilization and provide a faster end-user experience to visitors. To get familiar with caching concepts, simply review our ‘What is Caching?’ tutorial. Continue reading “Configure Apache 2 to Control Browser Caching”
- These instructions are intended specifically for solving the error: No matching DirectoryIndex (index.html) found.
- I’ll be working from both Liquid Web Core Managed CentOS 6 and CentOS 7 servers, and I’ll be logged in as root.
If you are used to administering Apache on a cPanel server, administering the faster Litespeed webserver is not that much different. Litespeed transparently takes over for Apache; any configuration changes that you would normally make in an Apache configuration file or .htaccess files is still made in those files. In fact, once Litespeed is installed you can administer your cPanel server like you normally would. The few changes you would want to make to Litespeed directly can be done through your server’s Web Host Manager (WHM).
Load balancing is the distribution of a workload across many nodes. In the web hosting industry, it is typically used for balancing HTTP traffic over multiple servers acting together as a web front-end. For the sake of this article, we will focus on the balancing of HTTP and HTTPS traffic through a Zeus Load Balancer.
‘Premature end of script headers’ can be an extremely vague error that leads to some headaches. Here are some suggestions that might help you fix the problem.
Using Softaculous, a new CMS(Content Management System) such as WordPress, Joomla, or Mambo has been installed on your website. It does not matter which CMS is installed, they all need to be able to write files on the server. However, they could show “permission denied” errors during the first-time setup or the first time an upload is attempted via their built-in web interface. This can happen when using DSO or CGI as the PHP handler. With either handler, php scripts by default run as the Apache user “nobody”, and the webserver software (usually Apache) needs to have write access to a user’s files to avoid this error.
The default Apache settings that cPanel sets upon install are definitely something that can be improved on. With a few small tweaks, the efficiency with which Apache runs with can be greatly improved.
Please noted: This article assumes that you are using a Linux server running Apache and cPanel or Plesk, and that you are familiar with editing files from the command line.