/usr/share/doc/nanoweb-doc/html/mod_proxy.html is in nanoweb-doc 2.2.9-0ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<TITLE>mod_proxy</TITLE>
<LINK REL="STYLESHEET" HREF="manual.css">
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#00003F" ALINK="#FF0000">
<DIV CLASS="body">
<DIV ALIGN="CENTER">
<A HREF="http://nanoweb.si.kz/"><IMG BORDER="0" SRC="/icons/nanoweb.png" ALT="[NANOWEB DOCUMENTATION]"></A>
<H3><SMALL>NANOWEB</SMALL>, the aEGiS PHP web server</H3>
</DIV>
<H1 ALIGN="CENTER">mod_proxy</H1>
With the nanoweb internal proxy server you can save download time as it
caches all requests gone through it. This is especially useful if you have a
local network with one internet gateway server which also works as firewall
to the local network (in this special case you are really encouraged to use
mod_proxy).
<br>
Beside its caching facility it can help you to filter unwanted content
(whole sites, images and popups as well).
<br>
<br>
In order to make use of mod_proxy, you have to make it loaded by nanoweb
by uncommenting the according <A HREF="core.html#loadmodule">LoadModule
directive</A> in the <tt>modules.conf</tt>; and you need of course to setup
proxy usage in all browsers you want to use on the computers of your local
network (use port 80 as for accessing nanoweb itself).
<br>
<br>
You may want to tweak the behaviour of mod_proxy with following directives:
<BR>
<H3><A NAME="proxyaccesslog">ProxyAccessLog directive</A></H3>
<B>Syntax:</B> ProxyAccessLog = /var/log/nanoweb/proxy.log <BR>
<B>Context:</B> Server Config <BR>
<P>
The proxy module generates an additonal seperate log file, as you probably
don't want the main server log to be intermixed with request informations
for files that are not located in your servers docroot.
</P>
<BR>
<H3><A NAME="proxyallowip">ProxyAllowIP directive</A></H3>
<B>Syntax:</B> ProxyAllowIP = 168.192. <BR>
<B>Context:</B> Server Config <BR>
<P>
Use this directive to allow hosts or all hosts from a network (with an
abbreviated IP address range) to access the www via the nanoweb internal
proxy server. Hosts not listed here cannot make use of the nanoweb proxy.
</P>
<BR>
<H3><A NAME="proxycachedir">ProxyCacheDir directive</A></H3>
<B>Syntax:</B> ProxyCacheDir = /var/cache/nanoweb <BR>
<B>Context:</B> Server Config <BR>
<P>
The proxy module of course needs a dedicated directory where it can save all
the files that were requested in the past, so that they do not need to be
fetched a second time from the real server if they get requested another
time.
</P>
<BR>
<H3><A NAME="proxydenysite">ProxyDenySite directive</A></H3>
<B>Syntax:</B> ProxyDenySite = /etc/nanoweb/badsites <BR>
<B>Context:</B> Server Config <BR>
<P>
If you want some servers not to be accessible through your proxy you just
need to list them in a text file (one server name per line) which you
specify here; so access to such servers will be forbidden.
</P>
<br>
<BR><HR NOSHADE COLOR="#063239">
<H3 ALIGN="CENTER"> <SMALL>NANOWEB</SMALL>, the aEGiS PHP web server </H3>
<DIV CLASS="navline"><A HREF="index.html">Index</A> <A HREF="modules.html">Modules</A> <A HREF="core.html">Configuration</A> <A HREF="../">READMEs</A> <A HREF="faq.html">FAQ</A> <A HREF="http://forums.t0x.net/viewforum.php?f=1">Support Forum</A></DIV>
</DIV>
</BODY>
</HTML>
|