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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<meta NAME="Author" CONTENT="Stefano Mazzocchi">
<title>Apache JServ Status</title>
</head>
<body BGCOLOR="#FFFFFF">
<p align="center"><a href="http://java.apache.org/" target="_top"><img SRC="../images/java-apache-project.gif" BORDER="0" WIDTH="609"
HEIGHT="100" ALT="The Java Apache Project"></a></p>
<h1 align="center">Apache JServ Status</h1>
<h3 align="left">Introduction</h3>
<p>One interesting feature of Apache JServ is that its main class, JServ.java, is a
servlet! Yes, it may seem strange, but Apache JServ is able to execute itself as a servlet
to output runtime information such as configurations and, in the future, enable remote
administration and runtime data such as load or number of servlets in use.</p>
<p>The Apache JServ Status is a collection of dynamically generated web pages that allow
the administrator to have a direct idea of the status of the system, on both the mod_jserv
module and on each connected servlet engine.</p>
<h3>Accessing the Apache JServ Status pages</h3>
<p>The Apache JServ Status front page is enabled by default in the example configurations
shipped in the distribution and it's mapped to the URI named <strong>/jserv/</strong>
(note the trailing slash!) in your main web server space (for most systems try <a
href="http://127.0.0.1/jserv/">http://127.0.0.1:80/jserv/</a> but the address and the port
are highly dependent on your web server configurations).</p>
<p>These pages give you the ability to check existing configurations remotely and control
the correct servlet engine behavior from a centralized information system.</p>
<p><strong><em>Warning</em>:</strong> even if the status pages are enabled in the sample
configuration files shipped with the distribution, you are strongly encouraged to deny the
access to this location on a production environment since this may give untrusted users
the ability to gather important system security information.</p>
<h3>Customizing the access to the Apache JServ Status pages</h3>
<p>Here it's shown a general list of web server directives that can be used to map the
Apache JServ status pages to a particular location. These are the directives used by the
Apache Web Server and may be placed in any of the three configuration files.</p>
<blockquote>
<pre><Location /status/jserv/>
SetHandler jserv-status
order deny,allow
deny from all
allow from dummy.org
</Location></pre>
</blockquote>
<p>The above directives map the Apache JServ status pages (SetHandler jserv-status) to the
URI /status/jserv/ (<location /status/jserv/>) allowing the access only from
requests coming from the "dummy.org" domain.</p>
<p>For more complex examples and documentation on how to restrict access to a particular
URI see the web server documents.</p>
<h3>Removing the Apache JServ Status pages</h3>
<p>Removing these page is just a matter of removing the above directives from the web
server configuration files.</p>
<p align="center"><font SIZE="-1">Copyright (c) 1997-99 <a HREF="http://java.apache.org/"
target="_top">The Java Apache Project</a>.<br>
$Id: howto.status.html,v 1.5 1999/06/09 05:21:28 jonbolt Exp $<br>
All rights reserved.</font> </p>
</body>
</html>
|
