新聞財經娛樂♬資訊 News Economy

 I am using Linux CentOS6.5 with apache VPS server with the following apache version which is reported from phpinfo() php function.

Question-1 from the apache version, whether it is told I have already installed mod_ssl apache module or not ? If yes, why I could not find anything in "httpd.conf" file  like as follows quotes

Why ?

And I am doing SSL self-cert installation for CentOS and follow  this link to do it.
https://library.linode.com/web-servers/apache/ssl-guides/centos, and I could
NOT install mod_ssl modules from "yum install mod_ssl" (Error report: no package available) but I can generate the self-cert and its key by openssl command.  Now I go to visit my site with https such as https://mysite.com that I can access the site index page but with red crossed mark and slash mark on https.

Question-2
I could not find the file of mod_ssl.so either at /usr/local/apache/modules or /usr/lib64/httpd or all my directories with my root access. Why my site still works for SSL https  access even there is no any apache mod_ssl module enabled or exists ?


Question-3. How can I install mod_ssl module  if yum install mod_ssl is not working ?

More my information provided: I had used Cpanel before on my hosting company and now I've switched to VPS server and stop to use Cpanel(since Cpanel was expired)

Duncan

Apache modules can be plugged into the Apache server in two different ways:

1. "Static"

-OR-

2. "Shared"

Static modules are compiled right into the server WHEN the server is built. You can't update them or change them in any way without re-compiling the Apache server.

Shared modules are compiled as separate files that end in ".so", like mod_ssl.so. The shared modules can be added to or removed from Apache at any time, which makes them more FLEXIBLE than static modules.

It is very similar to a car being built with an engine and seats and a steering wheel. Those are all pieces of the car that NEED to be in there for the car to run, so they are added when the car is built, and you cannot change them easily, but they are necessary pieces. Those pieces are like the "static" modules. They just become part of the car.

Then you have a stereo or radio in your car, which is ALSO probably added into the car when it is built, but it is designed so that anyone can easily remove the stereo and replace it. This is like a "shared" module.

Any module can be either static or shared, but there are usually many modules that are defaulted to being compiled into Apache statically. Static modules have a benefit of making Apache faster because they are loaded ONCE when Apache starts. Shared modules have to be loaded each time a child process is loaded, so they are slower.

Now, for your questions:

1. The Apache signature says mod_ssl, so mod_ssl -is- enabled. It is probably compiled statically, which is why you can't find a mod_ssl.so file. If you find your httpd binary, just run it like this:

httpd -M

That should tell you a full list of what modules are loaded and which are static or shared. If they are static, then you won't have a ".so" file because the code is INSIDE Apache.

2. When you use yum to install any Apache modules, you're going to be installing the shared versions. Don't try to install a shared module if you already have the module as a static module inside Apache. That said, I usually do this on my servers (in a cron job):

yum list > /root/yum.list

Then at any time, I can just use grep to quickly search for availability inside yum like this:

grep -i "mod_ssl" /root/yum.list
or
grep -i "ssl" /root/yum.list

If you don't have mod_ssl for some reason, then you may not have your yum repos set up properly.

3. Apache can be set up in different ways. You don't ALWAYS have to have a separate SSL config file. The config entries can go anywhere, and sometimes people have everything in one or two big config files for maintenance or performance reasons. Try searching your configs for "SSLEngine" or "SSLCertificateFile" and you might find your config entries for SSL.

4. Unless you add the self-signed certificate as a trusted root certificate to your own computer system (the one you're using to visit / test the web site), the browser will not recognize your self-signed certificate as a valid one. It will still allow HTTPS to work, but it is trying to warn you that it doesn't recognize the certificate. When you add the certificate to your own computer as a trusted root certificate and then close and reload your browser, you shouldn't get the red X over https anymore.