diff --git a/doc/adminguide.html b/doc/adminguide.html index 798d0ed5..e3bca407 100755 --- a/doc/adminguide.html +++ b/doc/adminguide.html @@ -162,11 +162,15 @@ Redirect permanent /elog http://your.host.domain/elog/ ProxyPass /elog/ http://your.host.domain:8080/
-Make sure that the Apache modules mod_proxy.c and mod_alias.c are activated. The Redirect
+Make sure that the Apache modules mod_proxy.c and mod_alias.c are activated. Justin Dieters <enderak@yahoo.com>
+reports that mod_proxy_http.c is also required. The Redirect
statement is necessary to automatically append a "/" to a request like
http://your.host.domain/elog. Apache then works as a proxy and forwards all requests
staring with /elog to the elogd daemon.
+Note: Do not put "ProxyRequests On" into your configuration file. This option is not necessary
+and can be misused for spamming and proxy forwarding of otherwise blocked sites.
+
Because elogd uses links to itself (for example in the email notification and
the redirection after a submit), it has to know under which URL it is running. If you run it
under a proxy, you have to add the line:
@@ -297,7 +301,8 @@ determined by the single elogd.cfg file in the ELOG i
This file may be edited directly from the file system, or from a form in the ELOG Web interface
(when the Config menu item is available). In this case, changes are applied dynamically without
-having to restart the server.
+having to restart the server. Instead of restarting the server, under Unix one can send a HUP signal
+like "killall -HUP elogd" to tell the server to re-read its configuration.
The many options of this unique but very important file are documented on the separate elogd.cfg syntax page.