<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Advanced .htaccess Tricks for Securing Sites</title>
	<atom:link href="http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html</link>
	<description>Advanced Web Development</description>
	<lastBuildDate>Wed, 18 Nov 2009 23:28:48 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John</title>
		<link>http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html#comment-60066</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 29 Jan 2009 04:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/?p=1916#comment-60066</guid>
		<description>Nice to see you&#039;re making progress, any ETA on the latest version? I can&#039;t wait! :D</description>
		<content:encoded><![CDATA[<p>Nice to see you&#8217;re making progress, any ETA on the latest version? I can&#8217;t wait! :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hal</title>
		<link>http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html#comment-59039</link>
		<dc:creator>hal</dc:creator>
		<pubDate>Sun, 25 Jan 2009 09:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/?p=1916#comment-59039</guid>
		<description>Interesting read.

A tip that springs to mind is that you can match *any* string in &lt;code&gt;RewriteRule&lt;/code&gt; and &lt;code&gt;RewriteCond&lt;/code&gt; directives with a regex start of line anchor (&lt;code&gt;^&lt;/code&gt;) used on its own.  This will perform better from a regex engine point of view.

For example, change a rule like this:
&lt;pre&gt;
RewriteRule .* - [L]
&lt;/pre&gt;
to this:
&lt;pre&gt;
RewriteRule ^ - [L]
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>Interesting read.</p>
<p>A tip that springs to mind is that you can match *any* string in <code>RewriteRule</code> and <code>RewriteCond</code> directives with a regex start of line anchor (<code>^</code>) used on its own.  This will perform better from a regex engine point of view.</p>
<p>For example, change a rule like this:</p>
<pre>RewriteRule .* - [L]</pre>
<p>to this:</p>
<pre>RewriteRule ^ - [L]</pre>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html#comment-58194</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Thu, 22 Jan 2009 06:10:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/?p=1916#comment-58194</guid>
		<description>Hey AskApache,

any info on the upgrade to your htaccess security plugin?

Eagerly looking fwd to it!
Eric</description>
		<content:encoded><![CDATA[<p>Hey AskApache,</p>
<p>any info on the upgrade to your htaccess security plugin?</p>
<p>Eagerly looking fwd to it!<br />
Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elaine</title>
		<link>http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html#comment-52648</link>
		<dc:creator>Elaine</dc:creator>
		<pubDate>Fri, 02 Jan 2009 23:24:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/?p=1916#comment-52648</guid>
		<description>&lt;p&gt;Hi there,&lt;/p&gt;

&lt;p&gt;I looked around your site but can&#039;t find what I am looking for. I need a &lt;strong&gt;&lt;code&gt;.htaccess&lt;/code&gt; url authentication script&lt;/strong&gt;. Something simple, not like PHP but just a couple of strings of code to put in &lt;code&gt;.htaccess file&lt;/code&gt; that would only allow secure page access from ssl site or https site only as well as internally from the same url and no one else is allowed unless they come from specific secure sites that I specify.&lt;/p&gt;

&lt;p&gt;Don&#039;t know how to explain this better, I am not technical ;-) Do you have anything like that not for wordpress but for self-hosted site written in html.&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>I looked around your site but can&#8217;t find what I am looking for. I need a <strong><code>.htaccess</code> url authentication script</strong>. Something simple, not like PHP but just a couple of strings of code to put in <code>.htaccess file</code> that would only allow secure page access from ssl site or https site only as well as internally from the same url and no one else is allowed unless they come from specific secure sites that I specify.</p>
<p>Don&#8217;t know how to explain this better, I am not technical ;-) Do you have anything like that not for wordpress but for self-hosted site written in html.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dvb</title>
		<link>http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html#comment-48263</link>
		<dc:creator>dvb</dc:creator>
		<pubDate>Sat, 20 Dec 2008 20:43:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/?p=1916#comment-48263</guid>
		<description>AskApache uses PHPBB?????

IMHO, MyBB is much better and more secured, worth a try.</description>
		<content:encoded><![CDATA[<p>AskApache uses PHPBB?????</p>
<p>IMHO, MyBB is much better and more secured, worth a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Peled</title>
		<link>http://www.askapache.com/htaccess/advanced-htaccess-tricks-for-securing-sites.html#comment-48234</link>
		<dc:creator>Ron Peled</dc:creator>
		<pubDate>Sat, 20 Dec 2008 17:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/?p=1916#comment-48234</guid>
		<description>While your method seems to work for a specific piece of software (phpBB) on your specific environment I like your general method of using whitelisting or use the path that is allowed instead of blocking what you believe is not allowed. This makes total sense. Thanks!</description>
		<content:encoded><![CDATA[<p>While your method seems to work for a specific piece of software (phpBB) on your specific environment I like your general method of using whitelisting or use the path that is allowed instead of blocking what you believe is not allowed. This makes total sense. Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
