<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
					xmlns:content="http://purl.org/rss/1.0/modules/content/"
					xmlns:wfw="http://wellformedweb.org/CommentAPI/"
				  >
<channel>
<title>Site apache-monitor.com  News RSS feed.</title>
<link>http://apache-monitor.com/</link>
<description><![CDATA[Site apache-monitor.com news and events. New software announcements and software updates]]></description>
<image><title>Site apache-monitor.com news and events. New software announcements and software updates</title>
<link>http://apache-monitor.com</link>
<url>http://cp.hs-lab.com/rss/apache-monitor.com.gif</url>
</image>
<language>en-us</language>
<pubDate>Thu, 17 May 2012 16:43:26 -0500</pubDate>
<item>
<title>How to monitor Apache web server traffic in real-time using apachetop</title>
<link>http://apache-monitor.com/articles/how-to-monitor-apache-web-server-traffic-in-real-time-using-apachetop.php</link>
<pubDate>Wed, 15 Sep 2010 05:13:01 -0500</pubDate>
<description><![CDATA[<p align="justify">
	<strong>Apachetop</strong> is a very useful program that displays the stats for Apache in real time. Apachetop can show you how many requests per second are coming in, what files have been accessed and how many times. It can also show you who is hitting the sites and where they are coming from.</p>
<p>
	<strong>1. Installing apachetop</strong></p>
<p>
	To install apachetop in <strong>CentOS</strong>, <strong>Fedora</strong>:</p>
<p>
	# yum install apachetop</p>
<p>
	Make sure you have <a href="http://dag.wieers.com/rpm/FAQ.php#B" target="_blank">DAG</a> repository enabled.<br />
	<span id="more-547"> </span><br />
	To install apachetop in <strong>Debian</strong>, <strong>Ubuntu</strong>:</p>
<p>
	# sudo apt-get install apachetop</p>
<p>
	To install apachetop in <strong>FreeBSD</strong>:</p>
<p>
	# cd /usr/ports/sysutils/apachetop/<br />
	# make install clean</p>
<p>
	<strong>2. Using apachetop</strong></p>
<p align="justify">
	apachetop essentially just watches the log files and constantly computes the stats. It can be set to show stats for the last set amount of time, or for the last set number of hosts.<br />
	It defaults to monitoring the defaults apache log file, but if you have virtual hosts, you will need to tell it to watch these also with the -f flag.</p>
<p>
	# apachetop -f /var/log/httpd/site1-access_log -f /var/log/httpd/site2-access_log</p>
<p align="justify">
	If your web server gets a low number of hits you can use the -N flag so that it shows you more information instead of clearing hits after 30 seconds. The -N flag sets the number of hits apachetop remembers. You can also use -T to change the length of time it remembers the hits.</p>
<p>
	This command will show stats for hits in the last 5 minutes.</p>
<p>
	# apachetop -N 300 -f /var/log/httpd/access_log</p>
<p>
	This command will have apachetop remember the last 100 hits and show the statistics for them.</p>
<p>
	# apachetop -T 100 -f /var/log/httpd/access_log</p>
<p align="justify">
	Once in apachetop the program will begin displaying and calculating the stats as they come in, so at first it will be blank. To switch between showing what files are getting hit, what hosts are accessing the web server, and where they are coming from press &quot;d&quot;.</p>
<p>
	For the help menu press &quot;h&quot;.</p>]]></description>
<author>support@apache-monitor.com (News and announcements)</author>
</item>
<item>
<title>What is HSLAB HTTP Monitor ?</title>
<link>http://apache-monitor.com</link>
<pubDate>Sat, 11 Sep 2010 07:51:27 -0500</pubDate>
<description><![CDATA[<p style="text-align: justify;">
	Real-time performance monitoring solution for Apache servers.<br />
	<br />
	<a href="http://apache-monitor.com" target="_blank">Company Website</a> : <a href="http://apache-monitor.com" target="_blank">http://apache-monitor.com</a><br />
	<br />
	HSLAB HTTP Monitor is a handy real-time performance monitoring and statistics analysis software application for Apache servers, which are used ubiquitously in the web hosting industry. Basically, with HSLAB monitoring system administrators always know who is currently connected (via connection tree), server operations distribution, amount of bandwidth being consumed, number of server requests per unit of time and other important server parameters.<br />
	<br />
	Most importantly, HSLAB HTTP Monitor is server-independent. That is the server running on Apache may be located thousands of miles away, while the program (HSLAB HTTP Monitor) could be installed on home or office PC and the system administrator will always have access to server&rsquo;s statistics or history real-time. This tool is very handy for many system administrators and web masters, because less then 1% of all servers are located in the same place where IT professionals work from.<br />
	<br />
	HSLAB HTTP Monitor shows all virtual servers being hosted, statistics for them and what files or documents are being accessed. There is an option to create a profile for each virtual server &ndash; a handy feature indeed. HSLAB HTTP Monitor shows what operations are being executed:<br />
	Waiting for Connection, Starting up, Reading Request; Sending Reply; Keepalive (read); DNS Lookup; Closing connection; Logging; Gracefully finishing; Idle cleanup of worker; Open slot with no current process.</p>]]></description>
<author>support@apache-monitor.com (News and announcements)</author>
</item>
<item>
<title>Apache VirtualHost Examples: Running several name-based web sites on a single IP address</title>
<link>http://apache-monitor.com/hslab-http-monitor-family.php</link>
<pubDate>Sat, 11 Sep 2010 07:48:05 -0500</pubDate>
<description><![CDATA[<p>
	Your server has a single IP address, and multiple aliases (CNAMES) point to this machine in DNS. You want to run a web server for www.example.com and www.example.org on this machine.</p>
<div class="note">
	<h3>
		Note</h3>
	<p style="text-align: justify;">
		Creating virtual host configurations on your Apache server does not magically cause DNS entries to be created for those host names. You <em>must</em> have the names in DNS, resolving to your IP address, or nobody else will be able to see your web site. You can put entries in your hosts file for local testing, but that will work only from the machine with those hosts entries.</p>
</div>
<div class="example">
	<h3>
		Server configuration</h3>
	<p>
		# Ensure that Apache listens on port 80<br />
		Listen 80<br />
		<br />
		# Listen for virtual host requests on all IP addresses<br />
		NameVirtualHost *:80<br />
		<br />
		<virtualhost :80=""><br />
		<span class="indent"> DocumentRoot /www/example1<br />
		ServerName www.example.com<br />
		<br />
		# Other directives here<br />
		<br />
		</span> </virtualhost><br />
		<br />
		<virtualhost :80=""><br />
		<span class="indent"> DocumentRoot /www/example2<br />
		ServerName www.example.org<br />
		<br />
		# Other directives here<br />
		<br />
		</span> </virtualhost></p>
</div>
<p style="text-align: justify;">
	The asterisks match all addresses, so the main server serves no requests. Due to the fact that www.example.com is first in the configuration file, it has the highest priority and can be seen as the default or primary server. That means that if a request is received that does not match one of the specified ServerName directives, it will be served by this first VirtualHost.</p>
<div class="note">
	<h3>
		Note</h3>
	<p>
		You can, if you wish, replace * with the actual IP address of the system. In that case, the argument to VirtualHost <em>must</em> match the argument to NameVirtualHost:</p>
	<div class="example">
		<p>
			NameVirtualHost 172.20.30.40<br />
			<br />
			<virtualhost 172.20.30.40=""><br />
			# etc ...</virtualhost></p>
	</div>
	<p>
		However, it is additionally useful to use * on systems where the IP address is not predictable - for example if you have a dynamic IP address with your ISP, and you are using some variety of dynamic DNS solution. Since * matches any IP address, this configuration would work without changes whenever your IP address changes.</p>
</div>
<p>
	The above configuration is what you will want to use in almost all name-based virtual hosting situations. The only thing that this configuration will not work for, in fact, is when you are serving different content based on differing IP addresses or ports.</p>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Name-based hosts on more than one IP address.</h2>
	<div class="note">
		<h3>
			Note</h3>
		<p>
			Any of the techniques discussed here can be extended to any number of IP addresses.</p>
	</div>
	<p>
		The server has two IP addresses. On one (172.20.30.40), we will serve the &quot;main&quot; server, server.domain.com and on the other (172.20.30.50), we will serve two or more virtual hosts.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			Listen 80<br />
			<br />
			# This is the &quot;main&quot; server running on 172.20.30.40<br />
			ServerName server.domain.com<br />
			DocumentRoot /www/mainserver<br />
			<br />
			# This is the other address<br />
			NameVirtualHost 172.20.30.50<br />
			<br />
			<virtualhost 172.20.30.50=""><br />
			<span class="indent"> DocumentRoot /www/example1<br />
			ServerName www.example.com<br />
			<br />
			# Other directives here ...<br />
			<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.50=""><br />
			<span class="indent"> DocumentRoot /www/example2<br />
			ServerName www.example.org<br />
			<br />
			# Other directives here ...<br />
			<br />
			</span> </virtualhost></p>
	</div>
	<p>
		Any request to an address other than 172.20.30.50 will be served from the main server. A request to 172.20.30.50 with an unknown hostname, or no Host: header, will be served from www.example.com.</p>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Serving the same content on different IP addresses (such as an internal and external address).</h2>
	<p style="text-align: justify;">
		The server machine has two IP addresses (192.168.1.1 and 172.20.30.40). The machine is sitting between an internal (intranet) network and an external (internet) network. Outside of the network, the name server.example.com resolves to the external address (172.20.30.40), but inside the network, that same name resolves to the internal address (192.168.1.1).</p>
	<p>
		The server can be made to respond to internal and external requests with the same content, with just one VirtualHost section.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			NameVirtualHost 192.168.1.1<br />
			NameVirtualHost 172.20.30.40<br />
			<br />
			<virtualhost 172.20.30.40="" 192.168.1.1=""><br />
			<span class="indent"> DocumentRoot /www/server1<br />
			ServerName server.example.com<br />
			ServerAlias server<br />
			</span> </virtualhost></p>
	</div>
	<p>
		Now requests from both networks will be served from the same VirtualHost.</p>
	<div class="note">
		<h3>
			Note:</h3>
		<p>
			On the internal network, one can just use the name server rather than the fully qualified host name server.example.com.</p>
		<p style="text-align: justify;">
			Note also that, in the above example, you can replace the list of IP addresses with *, which will cause the server to respond the same on all addresses.</p>
	</div>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Running different sites on different ports.</h2>
	<p style="text-align: justify;">
		You have multiple domains going to the same IP and also want to serve multiple ports. By defining the ports in the &quot;NameVirtualHost&quot; tag, you can allow this to work. If you try using <virtualhost name:port=""> without the NameVirtualHost name:port or you try to use the Listen directive, your configuration will not work.</virtualhost></p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			Listen 80<br />
			Listen 8080<br />
			<br />
			NameVirtualHost 172.20.30.40:80<br />
			NameVirtualHost 172.20.30.40:8080<br />
			<br />
			<virtualhost 172.20.30.40:80=""><br />
			<span class="indent"> ServerName www.example.com<br />
			DocumentRoot /www/domain-80<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.40:8080=""><br />
			<span class="indent"> ServerName www.example.com<br />
			DocumentRoot /www/domain-8080<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.40:80=""><br />
			<span class="indent"> ServerName www.example.org<br />
			DocumentRoot /www/otherdomain-80<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.40:8080=""><br />
			<span class="indent"> ServerName www.example.org<br />
			DocumentRoot /www/otherdomain-8080<br />
			</span> </virtualhost></p>
	</div>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />IP-based virtual hosting</h2>
	<p>
		The server has two IP addresses (172.20.30.40 and 172.20.30.50) which resolve to the names www.example.com and www.example.org respectively.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			Listen 80<br />
			<br />
			<virtualhost 172.20.30.40=""><br />
			<span class="indent"> DocumentRoot /www/example1<br />
			ServerName www.example.com<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.50=""><br />
			<span class="indent"> DocumentRoot /www/example2<br />
			ServerName www.example.org<br />
			</span> </virtualhost></p>
	</div>
	<p>
		Requests for any address not specified in one of the <virtualhost> directives (such as localhost, for example) will go to the main server, if there is one.</virtualhost></p>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Mixed port-based and ip-based virtual hosts</h2>
	<p style="text-align: justify;">
		The server machine has two IP addresses (172.20.30.40 and 172.20.30.50) which resolve to the names www.example.com and www.example.org respectively. In each case, we want to run hosts on ports 80 and 8080.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			Listen 172.20.30.40:80<br />
			Listen 172.20.30.40:8080<br />
			Listen 172.20.30.50:80<br />
			Listen 172.20.30.50:8080<br />
			<br />
			<virtualhost 172.20.30.40:80=""><br />
			<span class="indent"> DocumentRoot /www/example1-80<br />
			ServerName www.example.com<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.40:8080=""><br />
			<span class="indent"> DocumentRoot /www/example1-8080<br />
			ServerName www.example.com<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.50:80=""><br />
			<span class="indent"> DocumentRoot /www/example2-80<br />
			ServerName www.example.org<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.50:8080=""><br />
			<span class="indent"> DocumentRoot /www/example2-8080<br />
			ServerName www.example.org<br />
			</span> </virtualhost></p>
	</div>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Mixed name-based and IP-based vhosts</h2>
	<p>
		On some of my addresses, I want to do name-based virtual hosts, and on others, IP-based hosts.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			Listen 80<br />
			<br />
			NameVirtualHost 172.20.30.40<br />
			<br />
			<virtualhost 172.20.30.40=""><br />
			<span class="indent"> DocumentRoot /www/example1<br />
			ServerName www.example.com<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.40=""><br />
			<span class="indent"> DocumentRoot /www/example2<br />
			ServerName www.example.org<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.40=""><br />
			<span class="indent"> DocumentRoot /www/example3<br />
			ServerName www.example3.net<br />
			</span> </virtualhost><br />
			<br />
			# IP-based<br />
			<virtualhost 172.20.30.50=""><br />
			<span class="indent"> DocumentRoot /www/example4<br />
			ServerName www.example4.edu<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.60=""><br />
			<span class="indent"> DocumentRoot /www/example5<br />
			ServerName www.example5.gov<br />
			</span> </virtualhost></p>
	</div>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Using Virtual_host and mod_proxy together</h2>
	<p style="text-align: justify;">
		The following example allows a front-end machine to proxy a virtual host through to a server running on another machine. In the example, a virtual host of the same name is configured on a machine at 192.168.111.2. The <a href="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypreservehost%20on">ProxyPreserveHost On</a> directive is used so that the desired hostname is passed through, in case we are proxying multiple hostnames to a single machine.</p>
	<div class="example">
		<p>
			<virtualhost><br />
			ProxyPreserveHost On<br />
			ProxyPass / http://192.168.111.2<br />
			ProxyPassReverse / http://192.168.111.2/<br />
			ServerName hostname.example.com<br />
			</virtualhost></p>
	</div>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Using _default_ vhosts</h2>
	<h3>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />_default_ vhosts for all ports</h3>
	<p>
		Catching <em>every</em> request to any unspecified IP address and port, <em>i.e.</em>, an address/port combination that is not used for any other virtual host.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			<virtualhost><br />
			<span class="indent"> DocumentRoot /www/default<br />
			</span> </virtualhost></p>
	</div>
	<p>
		Using such a default vhost with a wildcard port effectively prevents any request going to the main server.</p>
	<p>
		A default vhost never serves a request that was sent to an address/port that is used for name-based vhosts. If the request contained an unknown or no Host: header it is always served from the primary name-based vhost (the vhost for that address/port appearing first in the configuration file).</p>
	<p>
		You can use <a href="http://httpd.apache.org/docs/2.2/mod/mod_alias.html#aliasmatch">AliasMatch</a> or <a href="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriterule">RewriteRule</a> to rewrite any request to a single information page (or script).</p>
	<h3>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />_default_ vhosts for different ports</h3>
	<p>
		Same as setup 1, but the server listens on several ports and we want to use a second _default_ vhost for port 80.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			<virtualhost _default_:80=""><br />
			<span class="indent"> DocumentRoot /www/default80<br />
			# ...<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost><br />
			<span class="indent"> DocumentRoot /www/default<br />
			# ...<br />
			</span> </virtualhost></p>
	</div>
	<p>
		The default vhost for port 80 (which <em>must</em> appear before any default vhost with a wildcard port) catches all requests that were sent to an unspecified IP address. The main server is never used to serve a request.</p>
	<h3>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />_default_ vhosts for one port</h3>
	<p>
		We want to have a default vhost for port 80, but no other default vhosts.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			<virtualhost _default_:80=""><br />
			DocumentRoot /www/default<br />
			...<br />
			</virtualhost></p>
	</div>
	<p>
		A request to an unspecified address on port 80 is served from the default vhost. Any other request to an unspecified address and port is served from the main server.</p>
</div>
<div class="top">
	&nbsp;</div>
<div class="section">
	<h2>
		<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Migrating a name-based vhost to an IP-based vhost</h2>
	<p>
		The name-based vhost with the hostname www.example.org (from our <a href="http://httpd.apache.org/docs/2.2/vhosts/examples.html#name">name-based</a> example, setup 2) should get its own IP address. To avoid problems with name servers or proxies who cached the old IP address for the name-based vhost we want to provide both variants during a migration phase.</p>
	<p>
		The solution is easy, because we can simply add the new IP address (172.20.30.50) to the VirtualHost directive.</p>
	<div class="example">
		<h3>
			Server configuration</h3>
		<p>
			Listen 80<br />
			ServerName www.example.com<br />
			DocumentRoot /www/example1<br />
			<br />
			NameVirtualHost 172.20.30.40<br />
			<br />
			<virtualhost 172.20.30.40="" 172.20.30.50=""><br />
			<span class="indent"> DocumentRoot /www/example2<br />
			ServerName www.example.org<br />
			# ...<br />
			</span> </virtualhost><br />
			<br />
			<virtualhost 172.20.30.40=""><br />
			<span class="indent"> DocumentRoot /www/example3<br />
			ServerName www.example.net<br />
			ServerAlias *.example.net<br />
			# ...<br />
			</span> </virtualhost></p>
	</div>
	<p>
		The vhost can now be accessed through the new address (as an IP-based vhost) and through the old address (as a name-based vhost).</p>
</div>
<div class="top">
	&nbsp;</div>
<h2>
	<img align="" alt="Якорь" src="images/spacer.gif?t=A7HG4HT" />Using the ServerPath directive</h2>
<p>
	We have a server with two name-based vhosts. In order to match the correct virtual host a client must send the correct Host: header. Old HTTP/1.0 clients do not send such a header and Apache has no clue what vhost the client tried to reach (and serves the request from the primary vhost). To provide as much backward compatibility as possible we create a primary vhost which returns a single page containing links with an URL prefix to the name-based virtual hosts.</p>
<div class="example">
	<h3>
		Server configuration</h3>
	<p>
		NameVirtualHost 172.20.30.40<br />
		<br />
		<virtualhost 172.20.30.40=""><br />
		<span class="indent"> # primary vhost<br />
		DocumentRoot /www/subdomain<br />
		RewriteEngine On<br />
		RewriteRule ^/.* /www/subdomain/index.html<br />
		# ...<br />
		</span> </virtualhost><br />
		<br />
		<virtualhost 172.20.30.40=""><br />
		DocumentRoot /www/subdomain/sub1<br />
		<span class="indent"> ServerName www.sub1.domain.tld<br />
		ServerPath /sub1/<br />
		RewriteEngine On<br />
		RewriteRule ^(/sub1/.*) /www/subdomain$1<br />
		# ...<br />
		</span> </virtualhost><br />
		<br />
		<virtualhost 172.20.30.40=""><br />
		<span class="indent"> DocumentRoot /www/subdomain/sub2<br />
		ServerName www.sub2.domain.tld<br />
		ServerPath /sub2/<br />
		RewriteEngine On<br />
		RewriteRule ^(/sub2/.*) /www/subdomain$1<br />
		# ...<br />
		</span> </virtualhost></p>
</div>
<p>
	Due to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#serverpath">ServerPath</a> directive a request to the URL http://www.sub1.domain.tld/sub1/ is <em>always</em> served from the sub1-vhost.<br />
	A request to the URL http://www.sub1.domain.tld/ is only served from the sub1-vhost if the client sent a correct Host: header. If no Host: header is sent the client gets the information page from the primary host.</p>
<p>
	Please note that there is one oddity: A request to http://www.sub2.domain.tld/sub1/ is also served from the sub1-vhost if the client sent no Host: header.</p>
<p>
	The <a href="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriterule">RewriteRule</a> directives are used to make sure that a client which sent a correct Host: header can use both URL variants, <em>i.e.</em>, with or without URL prefix.</p>
<p>
	Copyright 2006 The Apache Software Foundation.<br />
	Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a></p>]]></description>
<author>support@apache-monitor.com (News and announcements)</author>
</item>
<item>
<title>How to configure For Apache versions 2.2.x ?</title>
<link>http://apache-monitor.com/hslab-http-monitor-family.php</link>
<pubDate>Sat, 11 Sep 2010 07:45:53 -0500</pubDate>
<description><![CDATA[<div id="article_content">
	<p class="Default style3" style="font-weight: normal; color: rgb(0, 0, 0);">
		<span style="font-weight: normal; color: rgb(0, 0, 0);">First of all, you should be convinced, that your server uses the mod_status module. For this purpose open in your text editor a web server configuration file httpd.conf. Find the section loading modules and check up, whether there is there a line:</span></p>
	<p class="Default style3" style="color: rgb(255, 0, 0);">
		LoadModule status_module modules/mod_status.so</p>
	<p>
		This line can differ a little depending on the version of your server and operation system. If this line has ahead a symbol <span class="style3">#</span> that remove it.<br />
		&nbsp;</p>
	<p>
		Now you should locate lines:</p>
	<p>
		# Real-time info on requests and configuration<br />
		#Include conf/extra/httpd-info.conf</p>
	<p>
		and uncomment second line:</p>
	<p>
		# Real-time info on requests and configuration<br />
		Include conf/extra/httpd-info.conf</p>
	<p>
		<br />
		Now need to proceed to a configuration of the status. Open conf/extra/httpd-info.conf file and find the lines:</p>
	<p>
		#ExtendedStatus On</p>
	<p>
		Remove # symbol:</p>
	<p>
		ExtendedStatus On</p>
	<p>
		Check your domain name:</p>
	<p>
		&lt;Location /server-status&gt;<br />
		&nbsp;&nbsp; SetHandler server-status<br />
		&nbsp;&nbsp; Order deny,allow<br />
		&nbsp;&nbsp; Deny from all<br />
		&nbsp;&nbsp; Allow from .yourdomain.com<br />
		&lt;/Location&gt;</p>
	<p>
		Or for testing:</p>
	<p>
		&lt;Location /server-status&gt;<br />
		&nbsp;&nbsp; SetHandler server-status<br />
		&nbsp;&nbsp; Order deny,allow<br />
		&nbsp;&nbsp; Deny from all<br />
		&nbsp;&nbsp; Allow from all<br />
		&lt;/Location&gt;</p>
	<p class="Default">
		Line &quot;<span class="style3">Allow from .yourdomain.com</span>&quot; enables queries of the status from any computer of your domain(yourdomain.com). If you want to limit access only for the your computer, you should write &quot;<span class="style3">Allow from yourcomputer.yourdomain.com</span>&quot;. Where your computer is a name of your computer and yourdomain - a name of your domain. Also you can write &quot;<span class="style3">Allow from all</span>&quot;. In this case, the statistics of your wed server will be accessible from any computer in the Internet. <strong>We urgently do not recommend so to do, you should have very serious reason for this purpose!</strong></p>
	<p class="Default">
		Your web server configuration is finished! Now you should save your changes and restart your web the server.</p>
</div>]]></description>
<author>support@apache-monitor.com (News and announcements)</author>
</item>
<item>
<title>Announcing HSLAB HTTP Monitor Windows 7/Windows Server 2008 R2 Compatibility Status</title>
<link>http://apache-monitor.com/hslab-http-monitor-family.php</link>
<pubDate>Sat, 11 Sep 2010 07:29:06 -0500</pubDate>
<description><![CDATA[<p>
	<strong>For Release 17:48 GMT +2</strong><strong> 30.08.2010 </strong><strong>Handy Software Lab Releases New Version of its HSLAB HTTP Monitor, a handy real-time performance monitoring and statistics analysis software application for Apache web servers</strong></p>
<p>
	<a href="http://hs-lab.com/" target="_blank"><strong>Handy Software Lab</strong></a> today announced it will launch a new version of its application, <a href="http://www.sys-monitoring.com/products/am/hslab-http-monitor-family.php" target="_blank"><strong>HSLAB HTTP Monitor</strong></a>, which works with <strong>Microsoft Windows</strong><strong>7/Microsoft Windows Server</strong><strong>2008 R2 </strong>to offer customers enhanced security, as well as innovative user interface features and reliability improvements.With <strong><a href="http://www.sys-monitoring.com/products/am/hslab-http-monitor-family.php" target="_blank">HSLAB HTTP Monitor</a></strong>, administrators always know who is currently connected, server operations distribution, amount of bandwidth being consumed, and number of server requests per unit of time. Since software is server independent, server running on Apache may be located thousands of miles away from where program is installed. Software shows all virtual servers being hosted, statistics for them, and what files or documents are being accessed.</p>
<p>
	?Our ISV community is alive with innovation, and we?re committed to helping our partners drive the next generation of software experiences,? said Ross Brown, Vice President of ISV and Solutions Partners for the Worldwide Partner Group at Microsoft. ?Adding compatibility for the latest Microsoft operating systems helps ISVs to stay ahead of the competition and give their customers access to cutting-edge technologies.?</p>
<p>
	<a href="http://hs-lab.com/" target="_blank"><strong>Handy Software Lab</strong></a> is excited to launch this new version of <a href="http://www.sys-monitoring.com/products/am/hslab-http-monitor-family.php"><strong>HSLAB HTTP Monitor</strong></a>, said <strong>CEO</strong> at <a href="http://hs-lab.com/" target="_blank"><strong>Handy Software Lab</strong></a>. ?Making our application compatible with <strong>Microsoft Windows 7/Microsoft Windows Server 2008 R2 </strong>helps us offer our customers compelling benefits, including intuitive user interfaces, improved security and reliability features, full support for multi-core processing, sophisticated management features, flexible access administration.</p>
<p>
	<a href="http://hs-lab.com/" target="_blank"><strong>Handy Software Lab</strong></a>(HSLAB), founded in 1998 as a wholly-owned business is focused on the development, marketing, distribution and support of leading control and statistical software in a variety of application areas. Our software meets the needs of both corporate system administrators and home users. The company is capable of satisfy a consumer demand for high-quality and hi-tech software, at maintenance of secure online sales transactions, immediate delivery of a product and high-quality support.</p>
<p>
	HSLAB&#39;s award winning programs are powerful, designed with high-quality and extensive functionality, and presented in an easy-to-use graphical and command line interface designed to appeal to and fulfill the needs of administrators, power users and novices alike. HSLAB is continually working to improve existing products, as well as to produce new ones to satisfy every specific customer&#39;s needs. Whether you are looking for innovative software or software for process-control, security, or statistical software, HSLAB has products which will help you cope with the tasks you face.</p>]]></description>
<author>support@apache-monitor.com (News and announcements)</author>
</item>
<item>
<title>How to configure Apache versions 1.3.x - 2.0.x ?</title>
<link>http://kb.hs-lab.com/content/2/1/en/how-to-configure-apache-versions-13x-_-20x-.html</link>
<pubDate>Sat, 11 Sep 2010 07:24:47 -0500</pubDate>
<description><![CDATA[<p>
	First of all, you should be convinced, that your server uses the<br />
	mod_status module. For this purpose open in your text editor a web<br />
	server configuration file httpd.conf. Find the section loading modules<br />
	and check up, whether there is there a line:</p>
<p>
	LoadModule status_module modules/mod_status.so</p>
<p>
	This line can differ a little depending on the version of your server<br />
	and operation system. If this line has ahead a symbol # that remove<br />
	it.</p>
<p>
	Read more at<br />
	<a href="http://kb.hs-lab.com/content/2/1/en/how-to-configure-apache-versions-13x-_-20x-.html" rel="nofollow" target="_blank">http://www.hs-lab.com/usage/faq/content/2/1/en/how-to-configure-apach...</a></p>]]></description>
<author>support@apache-monitor.com (News and announcements)</author>
</item>
</channel>
</rss>
