ELOG/elog
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mention URL for stunnel etc

Browse Source 
SVN revision: 432
This commit is contained in:
ritt
2003-03-07 08:58:18 +00:00
parent 26a7b2b411
commit 040c413181
2 changed files with 32 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/adminguide.html
+15 -1
View File
@@ -146,11 +146,23 @@ ProxyPass /elog/ http://your.host.domain:8080/
Make sure that the Apache modules mod_proxy.c and mod_alias.c are activated. The <i>Redirect</i>
statement is necessary to automatically append a "/" to a request like <code><b>
http://your.host.domain/elog</code></b>. Apache then works as a proxy and forwards all requests
starint with <code><b>/elog</b></code> to the elogd daemon.<p>
staring with <code><b>/elog</b></code> to the elogd daemon.<p>
Because <code><b>elogd</b></code> 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:<br>
<ul><pre>
URL = http://your.proxy.host/subdir/
</pre></ul><p>
into elogd.cfg.<p>
Note that the variable $remote_host cannot be used inside elogd since the remote host is always
the proxy host (anybody knows how to fix that???).<p>
<h3><hr><i>Notes for the Solaris platform</i>:</h3>
<p><a href="mailto:huber@secaron.de">Martin Huber</a> reports that
@@ -287,6 +299,8 @@ on port 80, use a different port.
Substitute the port 80 if you started <code><b>elogd</b></code> on another port. This
causes <b><code>stunnel</code></b> to receive requests on the https port 443 and forward them to the <code><b>elogd</b></code> port.
<P>
<LI>Put the URL under which <code><b>elogd</b></code> runs into elogd.cfg:<p>
<pre>URL = https://your.host.name/</pre>
<LI>Connect to your logbook with a browser which supports SSL via:
<P>
<pre>https://your.host.name/</pre>
doc/config.html
+17 -7
View File
@@ -189,15 +189,25 @@ name you can get from your email program or your local system administrator.
This option specifies a filename which logs all login/logout activities and
successful user connections for logbooks with user level access.<p>
<LI><b><code>URL = &lt;http://host.domain&gt;</code></b>
<LI><b><code>URL = &lt;http[s]://host.domain[:port]/[subdir/]&gt;</code></b>
<br>
This URL is used in automatic email notifications to point back to the new message.
Usually, the elog daemon tries to obtain the URL from the "Referer" statement in the
HTTP header. If this is not correct (like if the domain name is missing), the URL used
to point back to the logbook can be overwritten by this statement. The URL has to
contain the port number if not the standard port 80 is used like<br>
If one of the three cases is true:<P>
<UL>
<LI><code><b>elogd</b></code> runs with <i>stunnel</i>
<LI><code><b>elogd</b></code> runs under a proxy
<LI>The automatic email notifications contains the wrong URL
</UL><p>
then the URL under which <code><b>elogd</b></code> is running has to be specified
manually with this statement. The URL has to
contain the port number if not the standard port 80 is used, it has to specify <i>https://</i>
if used under <i>stunnel</i>, and it has to contain the directory if used under a proxy like<br>
<br>
<code>URL = http://host.domain:8080/</code>
<table border=0 cellpadding=10>
<tr><td><code>URL = http://host.domain:8080/</code> <td>if running on port 8080</tr>
<tr><td><code>URL = https://host.domain/</code> <td>if running under <i>stunnel</i></tr>
<tr><td><code>URL = http://host.domain/subdir/</code> <td>if running under a proxy</tr>
</table>
<p>
<LI><b><code>Usr = &lt;name&gt;</code></b>