<?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>Albertech.net &#187; Apache</title>
	<atom:link href="http://albertech.net/category/apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://albertech.net</link>
	<description>Guides and Reviews for WordPress, PHP, MySQL, Apache, CMS Systems, jQuery, and other Technologies</description>
	<lastBuildDate>Fri, 11 May 2012 23:39:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Qualys SSL Labs &#8211; SSL web server testing</title>
		<link>http://albertech.net/2012/04/qualys-ssl-labs-ossl-web-server-testin/</link>
		<comments>http://albertech.net/2012/04/qualys-ssl-labs-ossl-web-server-testin/#comments</comments>
		<pubDate>Tue, 24 Apr 2012 19:49:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[ssl testing]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=963</guid>
		<description><![CDATA[Qualsys SSL Labs is a free resource to test your SSL web server configuration. It'll test for vulnerabilities, certificate validity, supported standards, and more.
<a href="https://www.ssllabs.com/ssltest/index.html" target="_blank">https://www.ssllabs.com/ssltest/index.html</a>

&#160;]]></description>
		<wfw:commentRss>http://albertech.net/2012/04/qualys-ssl-labs-ossl-web-server-testin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Modifying awstats to show total hits for matching files</title>
		<link>http://albertech.net/2011/11/modifying-awstats-to-show-total-hits-for-matching-files/</link>
		<comments>http://albertech.net/2011/11/modifying-awstats-to-show-total-hits-for-matching-files/#comments</comments>
		<pubDate>Thu, 03 Nov 2011 18:22:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[awstats]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[mods]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=829</guid>
		<description><![CDATA[<img class="alignnone size-full wp-image-830" title="Awstats with totals row added" src="http://albertech.net/wp-content/uploads/2011/11/awstats11.jpg" alt=""  />

Here's a quick modification to the awstats file that allows you to add a totals field for the "<strong>Viewed - Full List</strong>" option. There isn't a total hits field for matching files in awstats, so I added one to make it more useful. <strong>This makes it a lot quicker to total up hits for a specific folder, file type, or specific file in awstats</strong>.
]]></description>
		<wfw:commentRss>http://albertech.net/2011/11/modifying-awstats-to-show-total-hits-for-matching-files/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Setting up mod deflate on Apache2 for Debian to reduce server bandwidth</title>
		<link>http://albertech.net/2011/06/setting-up-mod-deflate-on-apache2-for-debian-to-reduce-server-bandwidth/</link>
		<comments>http://albertech.net/2011/06/setting-up-mod-deflate-on-apache2-for-debian-to-reduce-server-bandwidth/#comments</comments>
		<pubDate>Wed, 08 Jun 2011 17:28:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[apache2]]></category>
		<category><![CDATA[mod deflate]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=752</guid>
		<description><![CDATA[Mod deflate in Apache 2 is a great way to save on server bandwidth since it can compress files (js/xml/html/css) before it is sent to the client. Most web browsers support gzip compression (90%+) so this is a great way to reduce the amount of traffic sent by the server. It also helps with the Google Page Speed result.


View the full post for the configuration instructions.]]></description>
		<wfw:commentRss>http://albertech.net/2011/06/setting-up-mod-deflate-on-apache2-for-debian-to-reduce-server-bandwidth/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apache config for blocking proxy requests to random hostnames</title>
		<link>http://albertech.net/2011/06/apache-config-for-blocking-proxy-requests-to-random-hostnames/</link>
		<comments>http://albertech.net/2011/06/apache-config-for-blocking-proxy-requests-to-random-hostnames/#comments</comments>
		<pubDate>Fri, 03 Jun 2011 17:59:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[apache2 logs]]></category>
		<category><![CDATA[proxy]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=736</guid>
		<description><![CDATA[If you have an Apache server with strange logfile entries such as:

<code>GET http://proxyjudge1.proxyfire.net/fastenv HTTP/1.1" 404
GET http://images.google.com/ HTTP/1.1" 404
</code>

You need to reconfigure your Apache to deny any access  to a host that is not specifically configured on your server. This can be done via changing your /etc/apache2/sites-enabled/[your default config]
]]></description>
		<wfw:commentRss>http://albertech.net/2011/06/apache-config-for-blocking-proxy-requests-to-random-hostnames/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fix:  php_network_getaddresses: getaddrinfo failed: Name or service not known</title>
		<link>http://albertech.net/2011/05/fix-php_network_getaddresses-getaddrinfo-failed-name-or-service-not-known/</link>
		<comments>http://albertech.net/2011/05/fix-php_network_getaddresses-getaddrinfo-failed-name-or-service-not-known/#comments</comments>
		<pubDate>Tue, 31 May 2011 18:18:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[getaddrinfo]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=712</guid>
		<description><![CDATA[I ran across this error today after noticing a file_get_contents was not working. This was on a page that had been working fine for about a year.
"php_network_getaddresses: getaddrinfo failed: Name or service not known"

This issue is typically caused by the Apache/PHP host unable to contact the DNS server.

<strong>The first thing to check is to see if you can ping the remote host using console. </strong>
<ul>
	<li>If no, then your primary name server on /etc/resolv.conf (Debian) is not working. Find a working DNS and restart Apache.</li>
	<li>If yes, then Apache is still connecting to the broken DNS server. You should try restarting Apache ... ]]></description>
		<wfw:commentRss>http://albertech.net/2011/05/fix-php_network_getaddresses-getaddrinfo-failed-name-or-service-not-known/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Fix for Apache2 in Debian: Could not reliably determine the server&#8217;s fully qualified domain name</title>
		<link>http://albertech.net/2010/09/fix-for-apache2-in-debian-could-not-reliably-determine-the-servers-fully-qualified-domain-name/</link>
		<comments>http://albertech.net/2010/09/fix-for-apache2-in-debian-could-not-reliably-determine-the-servers-fully-qualified-domain-name/#comments</comments>
		<pubDate>Tue, 21 Sep 2010 22:31:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=457</guid>
		<description><![CDATA[If you get this warning message when you start up Apache (apache2), this means that you are missing the ServerName setting inside apache2.conf. By default, the install of Apache in Debian is doesn't include that setting in apache2.conf. The main reason is because they don't know what your server name will be.

<strong>To fix:</strong>
Open up <strong>/etc/apache2/apache2.conf</strong>

Add the following line:
<code>ServerName MyServer.com</code>

Replace "MyServer" with your server name. Restart Apache.

<strong>Note:</strong>
Its only looking for the setting inside apache2.conf.  It ignores the "ServerName" within a Virtual Host configuration block (such as in /etc/apache2/sites-enabled/000-default)]]></description>
		<wfw:commentRss>http://albertech.net/2010/09/fix-for-apache2-in-debian-could-not-reliably-determine-the-servers-fully-qualified-domain-name/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian: Installing Mailman with Exim4</title>
		<link>http://albertech.net/2009/09/debian-installing-mailman-with-exim4/</link>
		<comments>http://albertech.net/2009/09/debian-installing-mailman-with-exim4/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 21:03:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=283</guid>
		<description><![CDATA[I recently installed Mailman with Exim4, which was a challenge considering all the manual configuration you have to do. I found a few guides on the install, but they didn't seem to be "complete" enough to get the system working. Turns out, the biggest challenge was Exim4. The configuration files are confusing, especially since there are two sets of configuration files. ]]></description>
		<wfw:commentRss>http://albertech.net/2009/09/debian-installing-mailman-with-exim4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>awstats: Import old log files</title>
		<link>http://albertech.net/2009/09/awstats-import-old-log-files/</link>
		<comments>http://albertech.net/2009/09/awstats-import-old-log-files/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 16:26:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[awstats]]></category>
		<category><![CDATA[import]]></category>
		<category><![CDATA[old logs]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=256</guid>
		<description><![CDATA[One thing I've encountered with Awstats is adding in old apache log files. This is useful if you are migrating data from servers. By default, Awstats will ignore ALL past dates in the log that occur before the most recent log entry date. In order to avoid Awstats from finding the "recent log entry date", you will need move all Awstats cached files into a separate folder. ]]></description>
		<wfw:commentRss>http://albertech.net/2009/09/awstats-import-old-log-files/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Cleaner URLs in CodeIgniter</title>
		<link>http://albertech.net/2009/08/cleaner-urls-in-codeigniter/</link>
		<comments>http://albertech.net/2009/08/cleaner-urls-in-codeigniter/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 22:13:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[codeigniter]]></category>
		<category><![CDATA[rewrite]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=231</guid>
		<description><![CDATA[Here's a quick tip to make cleaner looking URLs in CodeIgniter PHP framework. By default, if you have an application, the path of the application usually ends after index.php.  Using Apache RewriteEngine, you can make cleaner looking URLs. You can have something similar to mysite.com/cigniter/MyApplication instead of mysite.com/cigniter/index.php/MyApplication]]></description>
		<wfw:commentRss>http://albertech.net/2009/08/cleaner-urls-in-codeigniter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress MU: Limit access to certain blogs</title>
		<link>http://albertech.net/2009/07/wordpress-mu-limit-access-to-certain-blogs/</link>
		<comments>http://albertech.net/2009/07/wordpress-mu-limit-access-to-certain-blogs/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 20:22:45 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[limit access]]></category>
		<category><![CDATA[wordpress mu]]></category>

		<guid isPermaLink="false">http://albertech.net/?p=203</guid>
		<description><![CDATA[I recently implemented a way to limit access by IP range on specific blogs on WordPress MU. As you know, WordPress MU uses Apache Rewrite engine to rewrite URLs. For instance, you have a blog on WordPress MU called "intranet". Apache Rewrite takes the "intranet" string in the URL and automatically rewrites it as a value in the PHP script. A side effect to Apache Rewrite is that "Directory" .htaccess parameters don't work. So, if you wanted only your company IPs to access an internal blog, you will need to use Apache Rewrite parameters instead. For the solution, read on...]]></description>
		<wfw:commentRss>http://albertech.net/2009/07/wordpress-mu-limit-access-to-certain-blogs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

