<?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>Crazy&#039;s Blog &#187; Apache</title>
	<atom:link href="http://blog.crazytje.be/tag/apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.crazytje.be</link>
	<description></description>
	<lastBuildDate>Sun, 28 Aug 2011 13:37:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Optimizing your web server: Part 1 &#8211; Gzip</title>
		<link>http://blog.crazytje.be/optimizing-your-webserver-part-1-gzip/</link>
		<comments>http://blog.crazytje.be/optimizing-your-webserver-part-1-gzip/#comments</comments>
		<pubDate>Sun, 22 Nov 2009 15:50:04 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[compression]]></category>
		<category><![CDATA[gzip]]></category>
		<category><![CDATA[optimalization]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=215</guid>
		<description><![CDATA[This will be the first blogpost in a compilation of posts about optimizing your webserver. Everyone likes their website to go fast right?, So did I. Something that can give you an easy performance boost is gzip compression. This compresses the data that is being send to the user with mod_deflate(apache). Because of the way <a href='http://blog.crazytje.be/optimizing-your-webserver-part-1-gzip/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/optimizing-your-webserver-part-1-gzip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apache: mod_rewrite redirect when part of querystring matches</title>
		<link>http://blog.crazytje.be/apache-mod_rewrite-redirect-when-part-of-querystring-matches/</link>
		<comments>http://blog.crazytje.be/apache-mod_rewrite-redirect-when-part-of-querystring-matches/#comments</comments>
		<pubDate>Wed, 28 Oct 2009 20:49:28 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[mod_rewrite]]></category>
		<category><![CDATA[redirect]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=105</guid>
		<description><![CDATA[Recently a friend asked how to do a redirect with apache&#8217;s mod_rewrite if a part of the url&#8217;s query string matches. After allot of trail and error I came to a solution. Original Url: htpp://example.com/old/index.php?param1=first&#38;param2=sometext In this url the param1=first is static so won&#8217;t change. The second parameter is not static, so it must not <a href='http://blog.crazytje.be/apache-mod_rewrite-redirect-when-part-of-querystring-matches/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/apache-mod_rewrite-redirect-when-part-of-querystring-matches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP Opcode caching: Why use an opcode cacher?</title>
		<link>http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/</link>
		<comments>http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 17:12:09 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[APC]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[apc]]></category>
		<category><![CDATA[eaccelerator]]></category>
		<category><![CDATA[opcode caching]]></category>
		<category><![CDATA[xcache]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=45</guid>
		<description><![CDATA[Why use an opcode cacher? When users surf to the website(s) hosted on your machine, the php files are compiled each time. Compiling the php code you worked so hard to develop takes time, and the more files you have, the longer it takes. This is especially the case when using PHP frameworks(personally I use <a href='http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

