<?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/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HTTP Blog &#187; Apache</title>
	<atom:link href="http://www.httpblog.com/category/web-servers/apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.httpblog.com</link>
	<description>Blog about content delivery, web servers, dedicated servers and hosting industry.</description>
	<lastBuildDate>Tue, 17 Aug 2010 16:22:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Apache settings for prefork.c</title>
		<link>http://www.httpblog.com/apache-settings-for-preforkc/</link>
		<comments>http://www.httpblog.com/apache-settings-for-preforkc/#comments</comments>
		<pubDate>Fri, 30 Jan 2009 19:28:24 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/?p=204</guid>
		<description><![CDATA[We use a medium busy server and do prefer to run prefork.c module with the following settings: StartServers 20 MinSpareServers 5 MaxSpareServers 20 ServerLimit 200 MaxClients 200 MaxRequestsPerChild 25000 The server is Dual Core Pentium with 2GB RAM and it&#8217;s not very busy server but does perfect. &#169; more great tips and resources onHTTP technology]]></description>
		<wfw:commentRss>http://www.httpblog.com/apache-settings-for-preforkc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Redirecting users to different page or site using mod_rewrite</title>
		<link>http://www.httpblog.com/redirecting-users-to-different-page-or-site-using-mod_rewrite/</link>
		<comments>http://www.httpblog.com/redirecting-users-to-different-page-or-site-using-mod_rewrite/#comments</comments>
		<pubDate>Fri, 19 Jan 2007 14:50:33 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/33</guid>
		<description><![CDATA[OK, if you want to redirect user to a different page or even a site, you can easily do it using mod_rewrite rule set: RewriteCond %{HTTP_USER_AGENT} &#8220;Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)&#8221; [NC] RewriteRule ^(.*) http://yoursite.com/page.html [R=301,L] Will redirect all users with Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) to http://yoursite.com/page.html &#169; more great [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/redirecting-users-to-different-page-or-site-using-mod_rewrite/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>slammed with multiple downloads from one IP</title>
		<link>http://www.httpblog.com/slammed-with-multiple-downloads-from-one-ip/</link>
		<comments>http://www.httpblog.com/slammed-with-multiple-downloads-from-one-ip/#comments</comments>
		<pubDate>Sat, 04 Nov 2006 04:56:12 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/26</guid>
		<description><![CDATA[If your web site has been slammed with multiple downloads from one IP causing the web site to slow load due to CPU, memory or network stack, it&#8217;s time for an action. For apache users there is an easy workaround &#8211; you need mod_limitipconn module and you are set. Apache 1.3 and version 2 has [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/slammed-with-multiple-downloads-from-one-ip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>limiting apache bandwidth speed and traffic leechers</title>
		<link>http://www.httpblog.com/limiting-apache-bandwidth-speed-and-traffic-leechers/</link>
		<comments>http://www.httpblog.com/limiting-apache-bandwidth-speed-and-traffic-leechers/#comments</comments>
		<pubDate>Tue, 08 Aug 2006 06:22:43 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/24</guid>
		<description><![CDATA[At this time, there are quite a few modules available that will stop traffic leech and limit simultaneous connections, bandwidth based on files, virtual host and so on. mod_bw Apache 2 (also available for Windows platform): http://www.ivn.cl/apache/ mod_cband (Apache2): http://cband.linux.pl/ mod_bandwidth http://www.cohprog.com/v3/bandwidth/doc-en.html# &#169; more great tips and resources onHTTP technology]]></description>
		<wfw:commentRss>http://www.httpblog.com/limiting-apache-bandwidth-speed-and-traffic-leechers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>mod_security and suggested rules</title>
		<link>http://www.httpblog.com/mod_security-and-suggested-rules/</link>
		<comments>http://www.httpblog.com/mod_security-and-suggested-rules/#comments</comments>
		<pubDate>Mon, 07 Aug 2006 15:30:23 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/23</guid>
		<description><![CDATA[mod_security is a powerful attack shield that can block http requests based on pre-defined rules. It&#8217;s a nice shield against known software exploits (e.g. non-patched forums, scripts etc)&#8230; A non-aggresive rule set: # Turn the filtering engine On or Off SecFilterEngine On # Change Server: string SecServerSignature &#8220;Apache&#8221; # This setting should be set to [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/mod_security-and-suggested-rules/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Apache mod_mmap_static for super performance</title>
		<link>http://www.httpblog.com/apache-mod_mmap_static-for-super-performance/</link>
		<comments>http://www.httpblog.com/apache-mod_mmap_static-for-super-performance/#comments</comments>
		<pubDate>Tue, 25 Jul 2006 20:29:47 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/17</guid>
		<description><![CDATA[Ok here is the deal if you do not want to switch to other web server software (e.g. Cherokee, thttpd, roxen, boa, lighttpd) and want the best performance for serving static files that do not often change the best solution is to use mod_mmap_static module. This module is not compiled in by default and you [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/apache-mod_mmap_static-for-super-performance/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>MaxClients setting for Apache web server</title>
		<link>http://www.httpblog.com/maxclients-setting-for-apache-web-server/</link>
		<comments>http://www.httpblog.com/maxclients-setting-for-apache-web-server/#comments</comments>
		<pubDate>Mon, 24 Jul 2006 12:06:40 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/16</guid>
		<description><![CDATA[In httpd.conf there is a directive MaxClients that is usually defined ~ 150. This value allows to serve more simultaneous requests and process queue more faster. Please note that you will need to recompile apache httpd (you must edit the HARD_SERVER_LIMIT entry in httpd.h and recompile) in order to set it higher that 256. Remember [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/maxclients-setting-for-apache-web-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Apache modules and performance</title>
		<link>http://www.httpblog.com/apache-modules-and-performance/</link>
		<comments>http://www.httpblog.com/apache-modules-and-performance/#comments</comments>
		<pubDate>Tue, 18 Jul 2006 12:51:14 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/14</guid>
		<description><![CDATA[For best performance you need to strip down your apache binary &#8211; the less modules, the less memory used the better speed / performance you will get. If you are loading modules via DSO you can easily remove module from the loading list by commenting out the LoadModule option. If you have a module linked [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/apache-modules-and-performance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apache mod_status</title>
		<link>http://www.httpblog.com/apache-mod_status/</link>
		<comments>http://www.httpblog.com/apache-mod_status/#comments</comments>
		<pubDate>Sun, 16 Jul 2006 04:22:58 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/15</guid>
		<description><![CDATA[If you have mod_status support compiled in your apache (either statically or using DSO) and activated in httpd.conf file with ExtendedStatus On you are probably affecting your site and server performance because every request to apache (e.g. web site hit) will generate multiple queries to gettimeofday or times function/system call depending on your Operating System.Make [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/apache-mod_status/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apache MaxKeepAliveRequests</title>
		<link>http://www.httpblog.com/apache-maxkeepaliverequests/</link>
		<comments>http://www.httpblog.com/apache-maxkeepaliverequests/#comments</comments>
		<pubDate>Mon, 10 Jul 2006 19:20:41 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/13</guid>
		<description><![CDATA[The option MaxKeepAliveRequests specifies the number of requests allowed per connection when the KeepAlive on has been set. When the value of this option is set to 0 then unlimited requests are allowed on the server. For better server performance, it&#8217;s recommended to allow unlimited requests or you can always define it with a high [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/apache-maxkeepaliverequests/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Boosting apache performance. Keepalive On or Off ?</title>
		<link>http://www.httpblog.com/boosting-apache-performance-keepalive-on-or-off/</link>
		<comments>http://www.httpblog.com/boosting-apache-performance-keepalive-on-or-off/#comments</comments>
		<pubDate>Thu, 06 Jul 2006 13:13:40 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/9</guid>
		<description><![CDATA[Boosting apache performance in high load environments. I suggest decreasing timeout value and keepalivetimeout, as well as other values listed and described below. Original timeout has been set to 300 by default. I suggest decreasing it to 120 (2 minutes) so all connections will timeout after 2 minutes. period. Timeout 120 By default, keepalive is [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/boosting-apache-performance-keepalive-on-or-off/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Quick steps to improving Apache performance</title>
		<link>http://www.httpblog.com/quick-steps-to-improving-apache-performance/</link>
		<comments>http://www.httpblog.com/quick-steps-to-improving-apache-performance/#comments</comments>
		<pubDate>Tue, 04 Jul 2006 06:56:26 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/8</guid>
		<description><![CDATA[Below, I have compiled a quick steps to make your Apache run faster and with better performance. 1.) When you are compiling turn off all the features and modules you do not need. The less the better. 2.) Turn off DNS logging with "HostnameLookups off" in httpd.conf file 3.) If you have .htaccess definitions, if [...]]]></description>
		<wfw:commentRss>http://www.httpblog.com/quick-steps-to-improving-apache-performance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is Apache?</title>
		<link>http://www.httpblog.com/what-is-apache/</link>
		<comments>http://www.httpblog.com/what-is-apache/#comments</comments>
		<pubDate>Sat, 01 Jul 2006 22:12:20 +0000</pubDate>
		<dc:creator>http guy</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://www.httpblog.com/6</guid>
		<description><![CDATA[Apache is a free and open source commercial grade web server software that according to Netcraft is the number #1 server that is powering millions of web sites and growing. Web site URL: http://www.apache.org Ps. even this web site is hosted using Apache web server daemon! &#169; more great tips and resources onHTTP technology]]></description>
		<wfw:commentRss>http://www.httpblog.com/what-is-apache/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
