ServerWatch content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.
As long as the server started, we can request a page. Pick your favorite Web
browser and make the request http://localhost:PORT, where
PORT is the value you specified above. The page that is returned should
be the index for the htdocs/ directory. The default index page is
index.html, but Apache does not install this file. Apache installs
twenty-five index.html files, each in a different language.
Because Apache 2.0 does not turn Mutli-views on by default, the default
configuration can not determine which file to use as the index page. To see the
default start page in English, request
http://localhost:PORT/index.html.en.
Setting Up Apache 2.0
Setting up Apache 2.0 is very much like setting up Apache 1.3. Everything is
controlled by the httpd.conf file, which is plain text. There are
very few differences, but the differences are important. The biggest difference
is the number of directives in the default
2.0 configuration file. This is important, because there is a different
container for each MPM. Different MPMs have
different configuration directives, so this is important. Current Apache 1.3
configuration files will only work with 2.0 if it is configured to use the
Prefork MPM. All of the other MPMs have different configuration directives, and
they remove some of the old 1.3 directives. The directives that are implemented
by the Prefork MPM are listed in the configuration snippet below. If Apache 2.0
is configured to use the MPMT_Pthread MPM then the other directives listed
below are implemented:
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 20
MaxRequestsPerChild 0
StartServers 5
MaxClients 8
MinSpareThreads 5
MaxSpareThreads 10
ThreadsPerChild 20
MaxRequestsPerChild 0
Conclusion
Hopefully after this article you will be able to download and install
Apache 2.0. With a little work, it should also be possible to migrate an
existing Apache 1.3 installation to an installation of the latest 2.0 alpha. If
you are interested in getting a jump on Apache 2.0, there is no better time
than now to jump in.
