You will have a binary file called httpd in the src directory. A binary distribution of Apache will supply this file.
The next step is to install the program and configure it.
Apache is designed to be configured and run from the same set of directories where it is compiled.
If you want to run it from somewhere else, make a directory and copy the conf, logs and icons directories into it.
The next step is to edit the configuration files for the server.
This consists of setting up various directives in up to three central configuration files. By default, these files are located in the conf directory and are called srm.conf, access.conf and httpd.conf.
To help you get started there are same files in the conf directory of the distribution, called srm.conf-dist, access.conf-dist and httpd.conf-dist. Copy or rename these files to the names without the -dist.
Then edit each of the files. Read the comments in each file carefully.
Failure to setup these files correctly could lead to your server not working or being insecure.
You should also have an additional file in the conf directory called mime.types. This file usually does not need editing.
First edit httpd.conf. This sets up general attributes about the server:
the port number, the user it runs as, etc. Next edit the srm.conf file; this sets up the root of the document tree, special functions like server-parsed HTML or internal imagemap parsing, etc. Finally, edit the access.conf file to at least set the base cases of access.
In addition to these three files, the server behavior can be configured on a directory-by-directory basis by using .htaccess files in directories accessed by the server.
KeepAlive Requests Persistent connections Multiple requests over one TCP socket Directives: KeepAlive MaxKeepAliveRequests KeepAliveTimeout
Apache 2.0 Filters Greg Ames Jeff Trawick
Agenda Why filters? Filter data structures and utilites An example Apache filter Filter types Configuration directives
Agenda cont... Frequently used Apache filters Output filters Input filters Pitfalls ways to avoid them mod_ext_filter Debugging hints The big filter list
Why filters? Same idea as Unix command line filters: ps ax | grep "apache.*httpd" | wc -l Allows independent, modular manipulations of HTTP data stream if a 1.3 CGI creates SSI or PHP tags, they aren't parsed CGI created SSI tags can be parsed in 2.0 possible Zend issue w/PHP at present
The general idea
Filter utilities and structures ap_register_[input|output]_filter creates ap_filter_rec_t ap_add_[input|output]_filter[_handle] creates ap_filter_t ap_pass_brigade passes a bucket brigade to the next output filter ap_get_brigade gets a bucket brigade from the next input filter