Configure the Server
Once you have the programs in place, you must configure the server to do what
you want it to. Go back to your books, reread the Web pages, and decide. Do you
want to allow users to have control of their own pages? It's an option, and it
may present a security issue. Same for server-side includes, which also may
consume excessive computer time (but they can be useful). Decisions, decisions,
decisions.
For the NCSA httpd, the configuration files are:
- httpd.conf - the primary configuration file.
- srm.conf - the server resource map.
- access.conf - configures security.
- mime.types - document type info
Remember that some of the options may be compiled in. Read the documentation!
Some recommendations:
- Put files in the default locations. This should simplify installation.
If you must put files in special locations, use symbolic links in the default
locations.
- Try server-side includes. They add a lot of capability, at only a slight
cost of computer power.
- Compile in the XBITHACK. This allows server-side includes for any
file with the execute permission bits set.
Ben Spade
Not responsible for errors in spelling or facts.