Specify the filename of the per-directory config files to use. This is .nwaccess per default, but you may want to set it to .htaccess so nanoweb uses the files you previously used with apache.
Gives the prefered RBL query method. The default "dns" is much faster than
the http access method "web".
See also mail-abuse.org/rbl for
further informations on the RBL system.
You can append additional headers to the HTTP responses nanoweb sends back
to the client (browser).
This directive can of course be used in [vhosts] configurations too.
nanoweb cannot be utilized to access other files than these located above any docroot (main server and virtual host ones). This directive set to 1 allows to access files pointed to via symlinks regardless of their location in the filesystem.
Any CGI may be called with a »pathinfo« appended to its filename (think of http://www.example.com/cgi-bin/program.php/arg1/arg2), which is treaten by many CGI interpreters as additional data input beside the »query string«.
Sets the filename of the HTTP authentication data file. If a file with this
name is present in the requested page's directory, the browser will be asked
for authentication. Authentication file format is almost the same as apache .htpasswd:
first line : realm name
other lines : login:des_encrypted_password
Allows to view the source of .bsp scripts when ?source is appended to the requested file.
If you plan to use the CGI version of PHP you should leave this enabled, as there still is a unfixed bug in PHP-CGI that forbids passing the PATH_INFO server var to the scripts.
The absolute maximum time (in seconds) a child process is allowed to live.
When the server cannot determine a MIME-type by examining the extensions of the requested file, it will tell the client the file is of the type set with this directive. The default of text/plain may not always match your requirements, so setting this value to text/html can do a better job in some cases.
With this directive you may specify one or more files, which get sent in
favour of a directory listing if found in it. This directive may also be
used in the per-directory configuration files (.nwaccess)
You may want to set it to just "index" if you activated
mod_multiviews, as this is more flexible.
Base directory path nanoweb will serve files from.
This directive needs to be present in each
virtual host configuration part.
Files to send on errors instead of the default (built-in) messages of nanoweb. These documents have to reside in the docroot.
Descriptions of each file out of a directory may be given in the file
specified here. Such a description file should look like:
filename.ext desc of this file
file2 ...
This tells mod_fb to include files which names start with a dot to be included in directory listings. On UNIX machines these »dotfiles« should be treaten as invisible files by standard programs; and because nanoweb keeps some of its per-directory configurations in .nwaccess and .nwauth you probably want to set this directive to the default of 1.
Directory listings are sorted by mod_fb according to this setting (»name« is the default). The use of »desc« reverses the order.
Whenever a directory listing (»filebrowser«) is to be sent back to the client, the server searches for a file with the hereby given name to be included in the sent output.
Is to activate / disactivate the automatic generation of directory listings by the server.
Default group server will run as.
This directive allows you to enable/disable mod_gzip for each virtual host or different directories (in .nwaccass).
Max compression ratio (percentage of original size). If it is higher, the content is likely to be already compressed and does not need a recompression.
Use reverse-DNS to put hostnames instead of IP addresses into server log.
Note that using DNS slows down nanoweb a bit, so if you need some more speed
you should think about disabling this feature, as you can get the names of
the hosts that requested pages from your server also later by evaluating the
server logs with appropriate software.
Sewtting this directive to 1 will make nanoweb to ignore .xxx files. This if for security reasons (not allowing clients to request .nwaccess or .nwauth files for example). You shouldn't change this unless you know exactly what you're doing.
This directive reads another (swapped out) configuration file into the current one. In standard installations the main configuration file is /etc/nanoweb/nanoweb.conf which additionally loads modules.conf and vhosts.conf.
Maximum number of http requests per connection (A client may get more than one file after it opened a connection to nanoweb, to speed up downloading of multiple files). To disable the keep-alive feature of nanoweb just set this value to 0.
Content-negotiation occurs if the requested file does not exist, but some variants can be found instead. If the client doesn't specifies a preferred language this setting will come into use.
Specify the IP address the server shall listen to for incoming connections.
Specify the TCP port number the server shall listen on for incoming connections. 80 is the default for web servers, but 8080 is also very common.
Maximum number of queued connections.
This directive is usually found in
You need to specify the full pathname of the PHP source file containing the
module.
Specifies file where nanoweb notes all served requests.
Logger Process support. If enabled, nanoweb will spawn logger processes at launch and all logging will be done by them. This can help if you are using User or Group directives or simply want more performance from the server. Set to the number of loggers you want, or 0 to disable.
User the nanoweb loggers will run as.
Group the nanoweb loggers will run as.
Logs every hit to standard output. Of course this requires you not to run nanoweb in daemon mode via nanoctl start, you need to run nanoweb.php from shell.
The mispell module handles incorrectly entered URLs. If a file with the given name cannot be found on the server it tries to figure out the correct name by checking the sounding of the filename against that of the files located on the server. This directives says what to do if it finds the correct name for the requested file. Default is »advice« which sends back an error page to the user, presenting him the corrected URL. You can also specify »redirect« which will send back a HTTP redirection response to the browser, so the users browser automagically re-requests with the corrected URL.
Reads in the system-wide available MIME-types database from given file, and thus makes nanoweb recognize hundreds of file extensions.
The mysqllog module saves request hits to a database instead of saving it to files as mod_stdlog does. So you need to give a hostname here, where a MySQL database server runs on.
Sets the name of the MySQL database for request logging.
You need an account for access to a MySQL database server.
You need an account for access to a MySQL database server.
You should leave this set to "server", as most browsers don't support agent-driven content-negotiation and just will present the error page sent to them for this case.
These gives additional preferences that will help mod_multiviews in selecting the "best" variant when the browser didn't send an Accept: header. Not that you can mix file extensions (without dot!) and mime types; quality-values help a lot.
Defines which extensions will be parsed and how.
Valid types are defined by the modules you loaded. Parameters are type
dependant (CGI takes path to CGI program, FCGI to FastCGI server socket,
while SSI doesn't requires a parameter).
This directive gives CGI extensions that should be checked for if a file
with a pathinfo is requested but no file extension is there. You should use
multiple PathInfoTryExt lines, one for each CGI extension you would like to
leave out.
See also AllowPathInfo
This directive gives a filename where nanoweb logs which pid (=process id, on Unix systems) it runs under.
If a URL is rewritten via a RewriteRule or because of some content negotiation, this setting influences if the rewritten URL (or if unset the requested one) shall be presented in error messages that may occur.
Mappes the requested file name to real one by rewriting with usage of regular expressions pattern matching. Please refer to the modules` documentation for a short explanation.
Does additional checks before some RewriteRules are executed, so they may get skipped if this test fails.
Nanoweb will wait specified amount of time for receival of the actual http request after a TCP/IP connection was established, before it closes this connection again to not prevent others from correctly connecting.
Admin mail address present in most of the server generated pages (errors, status, directory listings).
This gives an additional DNS name the server shall listen to. There may be multiple of this but only one ServerName directive.
You may wish to run nanoweb in standalone mode in most cases. This is,
the nanoweb server is started to stay resident in memory and waiting for
incoming connections.
Another variant of using the nanoweb server is by invoking it via
inetd - the »internet superserver« used on many UNIX systems to startup
internet services on oncoming requests, which leads to some overhead and is
slower in general as one copy of nanoweb.php needs to be executed for each
requested file.
Default DNS-name of this server. You may append a port number to the name.
This is used to force nanoweb in single process mode. You should uncomment it when running in win32 or if your php binary was not compiled with pcntl.
This gives an IP of a host allowed to consult the server status through mod_status. Multiple lines with this directive may be specified; an incomplete IP address can be used to allow a range of host addresses to be granted access.
This specifies where nanoweb shall put temporary files into, so this directory should be read/writeable by the user/group nanoweb will run as.
Default user server will run as.
This is the subpath which nanoweb will look for in users homedir
when an URL like http://webserver/~user is requested.
This directive can be set in the global section or for each virtual host.
Commands specified with such directives are executed, if a worm is detected.
Please refer to the file README.mod_worms (in the docs/ directory of the
unpacked tarball) as mod_worms requires additional preparation to work.
Text that is sent to the offending IIS server console.