As promised, we’re going to be giving the hosting industry a tool for doing a proper “benchmark” as a means of evaluating your own WordPress capabilities in a standardized way. I’m going to start this post with a few definitions, since there has been a lot of misuse of the words and language in best practices.
Archive for the ‘Web Server’ Category
It’s no secret that the slower a page loads, the more likely a customer is to leave your site. With the newest enhancements to LiteSpeed Web Server and LiteMage Cache, you can rest easy knowing that all your visitors will experience the fastest load times ever!
It seems like we’re entering the YouTube era of benchmarking.
You know how you can go on YouTube and find someone who knows almost nothing about the subject they are posting a video about? Well, benchmarking these days is kind of like that…
LiteSpeed Technologies announces the release of a one-click script that quickly and easily supercharges your DigitalOcean Droplet’s WordPress setup. LiteSpeed’s cache performance delivers significant performance and scalability gains over the DigitalOcean default.
Today, HTTPoxy was discovered in the wild. This vulnerability affects some server-side web applications that run in CGI or CGI-like environments, such as some FastCGI configurations. So far, the PHP, Python, and Go languages are known to be affected by this.
The vulnerability is caused by conflicting namespaces. A CGI or FastCGI-like interface sets environment variables based on HTTP request parameters. These can override internal variables that are used to configure the application. Further explanation of this bug can be found on the httpoxy web page.
The latest Google Chrome version 44.0.2403.89 is currently redirecting all HTTP URLs to their HTTPS versions for certain web applications. This is caused by a bug in Chrome causing the “HTTPS: 1” header to be sent by default on every request. This is mainly causing problems for WordPress sites with the WooCommerce plugin installed as well as sites without HTTPS support. Because of WordPress and WooCommerce’s popularity, this bug may be affecting a large number of people.