Red Hat NETWORK PROXY SERVER 3.7 - Manuel d'utilisateur Page 26

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 101
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 25
16 Configuring Your Secure Web Server
tions ofall ofApache’s configuration options. For yourconvenience, short
descriptions of theconfiguration directivesused in yoursecureweb server
are provided in this manual.
When you are looking through your web server’s configuration files, be
aware that your default configuration includes both a non-secure web
server and a secure web server. The secure web server runs as a virtual
host, which is configured in the httpd.conf configuration file. For more
information about virtual hosts, see section 2.6 on page 36.
Please Note: We do not include FrontPage extensions, which would give
the Red Hat Secure Web Server the capability of working with Microsoft
FrontPage. Including FrontPage support is a problem for two reasons.
First, the Microsoft license prohibits the inclusion of the extensions in a
third party product. Secondly, the patch which would enable Apache to
include FrontPage extensions is a very serious security risk. Much of the
workaround involves granting root access, which is something that you
want to avoid for security’s sake. This type of risk should be unaccept-
able to anyone who is even somewhat concerned with the security of their
secure web server and their website.
2.1 Apache Configuration
/etc/httpd/conf/ is the default location for the Apache web server’s
configurationfiles: httpd.conf,srm.conf andaccess.conf. Allthree
of these files are well-commented and somewhat self-explanatory. You
will probably not need to change the information they contain, but you
should be familiar with their most important configuration options.
If you do need to configure your secure web server, you simply edit one
of the three files, then either reload, or stop and start your secure web
server. How to reload, stop and start your server is covered in section 2.7
on page 40.
Before you edit one of the configuration files, it is a good idea to first copy
the original file to something like httpd.confold (or to any name you
want). Then, if you make a mistakewhile you’re editing the configuration
file, you’ll have a backup to start over with.
Vue de la page 25
1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 100 101

Commentaires sur ces manuels

Pas de commentaire