Determine version of Apache

trackstar2000 · 08-06-2014, 10:52 AM

Hello,

How would I determine the version installed if there is any?

TIA,
TT

szboardstretcher · 08-06-2014, 11:01 AM

Typically:

Code:

[root@dev ~]# httpd -v
Server version: Apache/2.2.15 (Unix)
Server built:   Apr  3 2014 23:56:16

If you are using RHEL compatible OS, then rpm will help:

Code:

[root@dev ~]# rpm -qa|grep http
httpd-2.2.15-30.el6.centos.x86_64
httpd-tools-2.2.15-30.el6.centos.x86_64

trackstar2000 · 08-06-2014, 11:12 AM

Quote:

Originally Posted by szboardstretcher

[root@dev ~]# httpd -v
Server version: Apache/2.2.15 (Unix)
Server built: Apr 3 2014 23:56:16

Thanks, I will give a try.

trackstar2000 · 08-06-2014, 03:56 PM

I am getting this version below. I installed the OS last year but it was never used. Any good reference of how I can upgrade the Apache. I am going to do "yum update" for the system updates

Server version: Apache/2.2.15 (Unix)
Server built: May 13 2013 22:11:16

szboardstretcher · 08-06-2014, 04:20 PM

You might not need to get a newer version. The version of apache included in the RHEL clones might be an 'older' version, but all of the security updates and patches are backported to it. They continute to use the 'older' version because of its proven stability.

If you want something newer for compatibility with a program or something, you will have to install from source. This can cause issues with your package management system though,. along with the inability to install plugins for your compiled apache from package management. Once you build something from source, you are stuck building some newer dependencies from source. There are guides on how to do it though.

I prefer to stick to the existing packaged version.

trackstar2000 · 08-06-2014, 05:38 PM

Quote:

Originally Posted by szboardstretcher

You might not need to get a newer version. The version of apache included in the RHEL clones might be an 'older' version, but all of the security updates and patches are backported to it. They continute to use the 'older' version because of its proven stability.

If you want something newer for compatibility with a program or something, you will have to install from source. This can cause issues with your package management system though,. along with the inability to install plugins for your compiled apache from package management. Once you build something from source, you are stuck building some newer dependencies from source. There are guides on how to do it though.

I prefer to stick to the existing packaged version.

Thanks so much. I read on various sources and they say the same thing.