<?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>Random Musings of an Insane Mind &#187; Apache</title>
	<atom:link href="http://cd34.com/blog/tag/apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://cd34.com/blog</link>
	<description>This is my blog, there are many others like it but this one is mine.</description>
	<lastBuildDate>Thu, 02 Feb 2012 20:47:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Hackers bypass .htaccess security by using GETS rather than GET</title>
		<link>http://cd34.com/blog/web-security/hackers-bypass-htaccess-security-by-using-gets-rather-than-get/</link>
		<comments>http://cd34.com/blog/web-security/hackers-bypass-htaccess-security-by-using-gets-rather-than-get/#comments</comments>
		<pubDate>Fri, 10 Dec 2010 22:37:37 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Web Security]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[Zend Optimizer]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=1078</guid>
		<description><![CDATA[Last night I received an urgent message from a client. My machine has been hacked, someone got into the admin area, I need all of the details from this IP. So, I grepped the logs, grabbed the appropriate entries and saw something odd. 1.2.3.4 - - [09/Dec/2010:22:15:41 -0500] "GETS /admin/index.php HTTP/1.1" 200 3505 "-" "Mozilla/5.0 [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/web-security/hackers-bypass-htaccess-security-by-using-gets-rather-than-get/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Nginx to Apache?</title>
		<link>http://cd34.com/blog/infrastructure/nginx-to-apache/</link>
		<comments>http://cd34.com/blog/infrastructure/nginx-to-apache/#comments</comments>
		<pubDate>Sun, 23 May 2010 16:20:29 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Web Infrastructure]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[deadline]]></category>
		<category><![CDATA[fastcgi]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[php]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=939</guid>
		<description><![CDATA[A few months ago we had a client that wanted to run Nginx/FastCGI rather than Apache because it was known to be faster. While we&#8217;ve had extensive experience performance tuning various webserver combinations, the workload proposed would really have been better served with Apache. While we inherited this problem from another hosting company &#8212; he [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/infrastructure/nginx-to-apache/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>DDOS attack mitigation</title>
		<link>http://cd34.com/blog/webserver/ddos-attack-mitigation/</link>
		<comments>http://cd34.com/blog/webserver/ddos-attack-mitigation/#comments</comments>
		<pubDate>Mon, 26 Apr 2010 06:02:58 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Webserver Software]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[ddos]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Varnish]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=937</guid>
		<description><![CDATA[Today we had a DDOS attack on one of our clients. They were running prefork with mod_php5 with a rather busy application. While we initially started filtering IP addresses using iptables and a few crudely hacked rules, we knew something had to be done that was a little more permanent. Moving to MPM-Worker with PHP [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/webserver/ddos-attack-mitigation/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Varnish and Nginx with Joomla</title>
		<link>http://cd34.com/blog/webserver/varnish-and-nginx-with-joomla/</link>
		<comments>http://cd34.com/blog/webserver/varnish-and-nginx-with-joomla/#comments</comments>
		<pubDate>Sun, 28 Jun 2009 17:01:30 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Webserver Software]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[joomla]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=685</guid>
		<description><![CDATA[Recently we had a client that had some performance issues with a Joomla installation. The site wasn&#8217;t getting an incredible amount of traffic, but, the traffic it was getting was just absolutely overloading the server. Since the machine hadn&#8217;t been having issues before, the first thing we did was contact the client and ask what [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/webserver/varnish-and-nginx-with-joomla/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Combined Web Site Logging splitter for AWStats</title>
		<link>http://cd34.com/blog/programming/python/combined-web-site-logging-splitter-for-awstats/</link>
		<comments>http://cd34.com/blog/programming/python/combined-web-site-logging-splitter-for-awstats/#comments</comments>
		<pubDate>Fri, 29 May 2009 20:59:43 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Python]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[awstats]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=639</guid>
		<description><![CDATA[AWStats has an interesting problem when working with combined logging. When you have 500 domains and combined logfiles at roughly 2 gigabytes a day, awstats spends a lot of time shuffling through all of the log files to return the results. The simple solution appeared to be a small python script that read the awstats [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/programming/python/combined-web-site-logging-splitter-for-awstats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Varnish saves the day&#8230;. maybe</title>
		<link>http://cd34.com/blog/scalability/varnish-saves-the-day-maybe/</link>
		<comments>http://cd34.com/blog/scalability/varnish-saves-the-day-maybe/#comments</comments>
		<pubDate>Tue, 28 Apr 2009 04:41:09 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Scalability]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Varnish]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=631</guid>
		<description><![CDATA[We had a client that had a machine where apache was being overrun&#8230; or so we thought.  Everything pointed at this one set of domains owned by a client and in particular two sites with 100+ elements on the page.  Images, css, javascript and iframes composed their main page.  Apache was handling things reasonably well, [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/scalability/varnish-saves-the-day-maybe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nginx after one day and conversion of two more machines</title>
		<link>http://cd34.com/blog/scalability/nginx-after-one-day-and-conversion-of-two-more-machines/</link>
		<comments>http://cd34.com/blog/scalability/nginx-after-one-day-and-conversion-of-two-more-machines/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 20:16:59 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Scalability]]></category>
		<category><![CDATA[Webserver Software]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[openx]]></category>
		<category><![CDATA[phpadsnew]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=617</guid>
		<description><![CDATA[Nginx impressed me with the way it was written and its performance has impressed me as well. This one client has 3 machines that ran Apache2-mpm-worker with php5 running under fastcgi.  While page response time was good, the machines constantly ran at roughly 15% idle cpu time, with roughly 600mb-700mb of the ram used for [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/scalability/nginx-after-one-day-and-conversion-of-two-more-machines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Varnish and Apache2</title>
		<link>http://cd34.com/blog/scalability/varnish-and-apache2/</link>
		<comments>http://cd34.com/blog/scalability/varnish-and-apache2/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 20:07:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Scalability]]></category>
		<category><![CDATA[Webserver Software]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=615</guid>
		<description><![CDATA[One client had some issues with Apache2 and a WordPress site. While WordPress isn&#8217;t really a great performer, this client had multiple domains on the same IP and dropping Nginx in didn&#8217;t seem like it would make sense to solve the immediate problem. First things first, we evaluated where the issue was with WordPress and [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/scalability/varnish-and-apache2/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>First Impressions of Nginx</title>
		<link>http://cd34.com/blog/webserver/first-impressions-of-nginx/</link>
		<comments>http://cd34.com/blog/webserver/first-impressions-of-nginx/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 06:22:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Webserver Software]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[tux]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=613</guid>
		<description><![CDATA[When I did the testing last week, I didn&#8217;t expect overly dramatic results. Yes, replacing apache and moving to a FastCGI/PHP installation did seem to make sense and nginx definitely is designed to handle things well. The conversion of one virtualhost on that machine resulted in a few minor hitches. Rewrite rules are a little [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/webserver/first-impressions-of-nginx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apache, Varnish, nginx and lighttpd</title>
		<link>http://cd34.com/blog/infrastructure/apache-varnish-nginx-and-lighttpd/</link>
		<comments>http://cd34.com/blog/infrastructure/apache-varnish-nginx-and-lighttpd/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 15:33:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Web Infrastructure]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Lighttpd]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Varnish]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=606</guid>
		<description><![CDATA[I&#8217;ve never been happy with Apache&#8217;s performance.  It seemed that it always had problems with high volume sites.  Even extremely tweaked configurations resulted in decent performance to a point which then required more hardware to continue going.  While I had been a huge fan of Tux, sadly, Tux doesn&#8217;t work with Linux 2.6 kernels very [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/infrastructure/apache-varnish-nginx-and-lighttpd/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

