Testing The Certificate; Accessing The Server - Red Hat ENTERPRISE LINUX 4 System Administration Manual

Chapter 25. Apache HTTP Secure Server Configuration
After you provide the correct information, a self-signed certificate is created in /etc/httpd/conf/
ssl.crt/server.crt. Restart the secure server after generating the certificate with following the
command:
/sbin/service httpd restart

25.9. Testing The Certificate

To test the test certificate installed by default, either a CA-signed certificate, or a self-signed certificate,
point your Web browser to the following home page (replacing server.example.com with your
domain name):
https://server.example.com
Note
Note the s after http. The https: prefix is used for secure HTTP transactions.
If you are using a CA-signed certificate from a well-known CA, your browser probably automatically
accepts the certificate (without prompting you for input) and creates the secure connection. Your
browser does not automatically recognize a test or a self-signed certificate, because the certificate
is not signed by a CA. If you are not using a certificate from a CA, follow the instructions provided by
your browser to accept the certificate.
Once your browser accepts the certificate, your secure server displays a default home page.

25.10. Accessing The Server

To access your secure server, use a URL similar to the following:
https://server.example.com
Your non-secure server can be accessed using an URL similar to the following:
http://server.example.com
The standard port for secure Web communications is port 443. The standard port for non-secure Web
communications is port 80. The secure server default configuration listens on both of the two standard
ports. Therefore, do not need to specify the port number in a URL (the port number is assumed).
However, if you configure your server to listen on a non-standard port (for example, anything other
than 80 or 443), you must specify the port number in every URL which is intended to connect to the
server on the non-standard port.
For example, you may have configured your server so that you have a virtual host running non-
secured on port 12331. Any URLs intended to connect to that virtual host must specify the port
262