3 httpd.conf httpd.mtype \- configuration files for the Minix httpd web server
9 is the configuration file for the Minix httpd web server written by
10 Michael Temari. A sample version is included with the distribution
11 archive and is unpacked in the source directory (normally
12 .BI /usr/local/src/httpdxxx).
13 Also provided is an example
15 file. This is an extension of the main configuration file which is normally
16 included when the main file is read.
18 The makefile does not install
22 automatically. The sample files included in the distribution are only
23 examples, you must copy it and edit them for the needs of your own
25 .SH CONFIGURATION FILE FORMAT
27 is an ascii file which consists of lines of the following form:
29 .B directive LWS [parameters separated by LWS]
31 NOTE: LWS denotes Linear White Space which is spaces and/or tabs
32 .SH CONFIGURATION FILE DIRECTIVES
33 The following are valid configuration file directives (listed in the order
34 they appear in the sample
36 file provided in the distribution):
38 .B serverroot user chroot logfile dbgfile dirsend direxec vhost auth
39 .B proxyauth vpath include mtype
41 To make the file more readable, for directives which occupy multiple
42 lines you may eliminate the directive on lines after the first and begin
45 .SH DESCRIPTIONS OF DIRECTIVES
51 directive sets the translation for
60 directive causes the server to run as the given
62 otherwise the server will run as whoever started it (normally root).
68 directive causes the server to chroot to the given directory after
69 the configuration and log files have been opened. Normally this will be the
70 home directory of the given username in the user directive.
74 will be translated to the home directory of
79 will be translated to the serverroot directory.
81 NOTE: if this directive is used then beware of the consequences.
87 directive tells the server where to log http transactions.
89 NOTE: the log file must exist to enable logging.
95 directive tells the server where to log debugging of http transactions.
97 NOTE: the debug log file must exist to enable debug logging.
103 directive tells the server that when a directory is requested
104 that it should send the first file that it finds in the directory from the
112 directive tells the server that when a directory is requested
113 and no file is found from the
115 directive that it should run the given
118 NOTE: the program normally generates a directory listing on the fly using
123 NOTE: the program access is considered
125 with no access restrictions.
127 .B vhost hostname vhostroot
131 directive is for defining access for virtual hosts. If none are configured
132 then any host is accepted. If specified then access is only granted for
133 requests for hosts which are configured here. In the
137 gets translated to the corresponding
141 .B auth authname authdescription access [passwdfile [users]]
145 directive sets up different authorizations with the server. The
147 is the name given to the authorization and is case insensitive.
150 is the description of the authorization and is what
151 the user will see when asked to enter a username and password. The
152 access is one or more of
155 tells the server the URL can be read.
157 tells the server the URL can be overwritten.
160 that the URL can and should be executed. Access is in addition to normal
161 Unix security considerations. For instance a file that can be written to
162 that does not have the
164 access will have an error returned. The
166 is the name of the password file to validate users against. If
170 then the system password file
174 is given then no authorization is allowed for anyone. If no
176 are given then any validated user is authorized, otherwise only the given
180 .B proxyauth authname authdescription access [passwdfile [users]]
184 directive defines access authorization to be used for Proxy access.
193 = Must be R to allow proxy
201 .B vpath from to [auth [access]]
205 directive sets up URL path translations and authorizations. A
206 requested URL that matches
208 will be translated to
216 does not exist then the URL will have no
220 is not given then the access is taken from the
222 record (see above). A
226 means that the server should use a translation from another
228 record, but associate the given
230 and access with the requested URL. A
232 may be at the end only of the
234 to provide a wildcard match. For example if the
247 will not. The requested URL is first checked against each
249 record until an exact match (meaning URL match
255 is found or the end of the list. Therefore a wildcard match will match
257 .B from in the list in which it matched.
259 NOTE: if at the beginning of the to field
261 /~user will get translated to the home directory of the given user
263 // wile get translated to the serverroot directory
269 directive tells the server to read configuration information
270 from the given filename.
272 NOTE: normally you get
274 directives in an included file.
276 .B mtype mimetype extensions
280 directive tells the server what
282 to associate with files which have any of the given
284 If no match is found then the file will be treated as
285 .B application/octet-stream.
296 The source directory contains a commented sample
302 You can run the server as
303 .B httpd -t /etc/httpd.conf
304 to see whether the configuration file is being parsed correctly.
306 Although standard Minix does not have a graphical interface to support
307 browsers such as Netscape and Microsoft Internet Explorer, the
309 browser can be used on 32-bit Minix systems with enough memory. You can point
310 lynx to your own site to browse your own pages.
311 When debugging a web server there is nothing quite like browsing your own
312 pages to see whether things are working right. That said, be aware that
313 different web browsers may vary in how they interpet standard web page
314 features, and will certainly vary in how they interpret "extensions" to
315 the HTML standards. So checking a page with several browsers on several
316 platforms is always a good idea.
318 Not really a bug, but you can get in trouble if a real directory you want
319 to access shares the first part of its name with a
321 definition. You just have to pay attention to the directory names you use.
323 The Minix httpd server was created by and is maintained by Michael Temari
324 <Michael@TemWare.Com>
326 This man page was compiled by Al Woodhull <awoodhull@hampshire.edu>