Apache Http Server Version

Posted on  by admin

How to Check Apache Web Server Version in Linux. There are one or two commands to check the Apache web server version in Linux, depending on the Linux distribution you use. The apachectl command, which available in both Debian and RedHat based Linux distributions have -v option which prints the Apache version: apachectl -v. The Apache HTTP Server, has been updated from version 2.4.6 to version 2.4.37 between RHEL 7 and RHEL 8. This updated version includes several new features, but maintains backwards compatibility with the RHEL 7 version at the level of configuration and Application Binary Interface (ABI) of external modules. Enable server-status. The server-status page will also show this, in addition to performance information. It starts with something like this: Apache Server Status for localhost. Server Version: Apache/2.2.14 (Win32) PHP/5.3.1. Server Built: Sep 28 2009 22:41:08. See Detailed Instructions for server-status on another question.

Apache is a popular open-source, cross-platform web server that is, by the numbers, the most popular web server in existence. It’s actively maintained by the Apache Software Foundation.

Some high-profile companies using Apache include Cisco, IBM, Salesforce, General Electric, Adobe, VMware, Xerox, LinkedIn, Facebook, Hewlett-Packard, AT&T, Siemens, eBay, and many more (source).

In addition to its popularity, it’s also one of the oldest web servers, with its first release all the way back in 1995. Many cPanel hosts utilize Apache today. Like other web servers, Apache powers the behind-the-scenes aspects of serving your website’s files to visitors.

Because Apache doesn’t perform as well in some benchmarks, especially for static websites or websites with high traffic, Kinsta uses the NGINX web server instead of Apache. Though NGINX hasn’t been around for as long as Apache, it’s quickly grown in popularity and market share since its launch in 2004.

How Does Apache Work? Web Server Basics Explained

While there’s a lot of complexity underpinning how a web server functions, the basic job of all web servers is to accept requests from clients (e.g. a visitor’s web browser) and then send the response to that request (e.g. the components of the page that a visitor wants to see).

The Apache web server has modules which add more functions to its software, such as MPM (for handling multi-processing modes) or mod_ssl for enabling SSL v3 and TLS support (suggested reading: TLS vs SSL). Some common features seen in Apache include:

  • IPv6
  • FTP
  • Perl, Lua, and PHP
  • Bandwidth throttling
  • WebDAV
  • Load balancing
  • URL rewriting
  • Session tracking
  • Geolocation based on IP address
Server

While a web server is an essential part of any website, it’s important to note that casual WordPress users are unlikely to interact with their web server directly most of the time.

Http

Apache vs Nginx Usage Stats

When you look at every single website on the Internet, Apache is the most popular web server. It powers 47% of the websites with a known web server, according to W3Techs.

However, Apache’s usage greatly drops when you start looking at the web’s most highly trafficked sites. Apache only powers:

  • 27.1% of the 100,000 most popular sites
  • 21.5% of the 10,000 most popular sites
  • 16.2% of the 1,000 most popular sites

This drop-off likely stems, at least in part, from Apache’s lower benchmarks for high traffic websites.

Conversely, NGINX, the web server that Kinsta uses, is used by a majority of high-traffic sites, powering:

  • 56.1% of the 100,000 most popular sites
  • 63.2% of the 10,000 most popular sites
  • 57% of the 1,000 most popular sites

If you check the Google Search trends since 2004, you can see this trend play out where Apache’s popularity (as a search term) is decreasing while NGINX’s is creeping up.

Apache

How To Check Which Web Server You’re Using

If you want to see whether you’re using Apache or NGINX, you can often (but not always) look at your site’s HTTP header.

To view your site’s HTTP header, you can:

Apache http server version
  • Use the Network tab of Chrome Developer Tools
  • Use a tool like Pingdom or GTmetrix

Apache HTTP header

This method may not work if you’re using a service like Cloudflare, though.

Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

Apache Http Server Version 2.4

Apache http server version 6

If you enjoyed this tutorial, then you’ll love our support. All Kinsta’s hosting plans include 24/7 support from our veteran WordPress developers and engineers. Chat with the same team that backs our Fortune 500 clients. Check out our plans

Apache Httpd Latest Version

Copied from www.apachelounge.com/viewtopic.php?p=26636#26636 , thanks Anaksunaman.
If you are installing from zip files, the replacement should be fairly simple. The zip files from Apache Lounge are completely self-contained installs and need nothing additional to run out of the box (other than basic config file tweaking, etc. ).
Before upgrading, be careful to backup all your conf files/directories, SSL certificates/directories, virtual host files/directories, etc. or any other custom modifications to the server. Otherwise, you might run into a bunch of work!
A basic upgrade would likely consist of the following:
1.) Stop the Apache service.
2.) Rename your original Apache installation directory (e.g. rename 'C:installpathApache24' to something like 'C:installpathApache24_old'). This is your basic backup step.
3.) Unzip your new upgraded installation to the old install directory (e.g. 'C:installpathApache24').
4.) Copy needed conf files, additional components, etc. from the old install folder to the new install folder (e.g. select the needed files from 'Apache24_old' and copy them to 'Apache24').
If you are paranoid, you can always uninstall and reinstall the Apache service after step 4 if you like, but is unlikely to be necessary.
A big advantage to keeping the same installation directory is that it should obviate the need for making any conf changes (i.e. everything should be 'drag and drop' as far as replacing the new default config files with your old ones -- you may still want to keep the default files as backups though). Furthermore, you should be able to drop custom files (SSL certificates, modules, etc.) into the same locations and have them work as well.
A big advantage to this approach (simply renaming the old directory) is that you can also keep your old installation 'just in case'. As long as you don't cannibalize your old install to make it inoperable (i.e. you copy and DON'T cut/paste), you have a backup in case your upgrade goes awry for some reason.