<?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: Apache Authentication in htaccess</title>
	<atom:link href="http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html</link>
	<description>Advanced Web Development</description>
	<lastBuildDate>Thu, 18 Mar 2010 14:15:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: AK</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-124887</link>
		<dc:creator>AK</dc:creator>
		<pubDate>Wed, 10 Mar 2010 21:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-124887</guid>
		<description>Your &quot;Allow from IP without password prompt, and also allow from any address with password prompt&quot; example is exactly what I was looking for.  Thank you!</description>
		<content:encoded><![CDATA[<p>Your &#8220;Allow from IP without password prompt, and also allow from any address with password prompt&#8221; example is exactly what I was looking for.  Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apache Development</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-121288</link>
		<dc:creator>Apache Development</dc:creator>
		<pubDate>Sun, 28 Feb 2010 12:37:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-121288</guid>
		<description>I am encountering a problem where I get a 404 page every time I put Require valid-user into the .htaccess of a folder. Any ideas why this might be happening?</description>
		<content:encoded><![CDATA[<p>I am encountering a problem where I get a 404 page every time I put Require valid-user into the .htaccess of a folder. Any ideas why this might be happening?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: martin</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-111341</link>
		<dc:creator>martin</dc:creator>
		<pubDate>Tue, 24 Nov 2009 12:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-111341</guid>
		<description>Great article, thank you!</description>
		<content:encoded><![CDATA[<p>Great article, thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-110956</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Sun, 22 Nov 2009 19:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-110956</guid>
		<description>Bobby, create an .htaccess file in your wp-admin directory following the contents listed in &quot;Allow from IP without password prompt, and also allow from any address with password prompt&quot;.


The &quot;Allow from 172.17.10.1&quot; should contain your static IP address if you have one, or that of your client if you are building this site for someone else to access.  Of course, you can add more than one line in that format.  It will allow anyone arriving from an IP in the Allow statement(s) to access the WPAdmin login screen without having the enter the Apache Username/Password combination.  Everyone else will be stopped at the Apache login screen, and if they authenticate there they will then receive the WP login screen.  I do this on over 100 WP sites.</description>
		<content:encoded><![CDATA[<p>Bobby, create an .htaccess file in your wp-admin directory following the contents listed in &#8220;Allow from IP without password prompt, and also allow from any address with password prompt&#8221;.</p>
<p>The &#8220;Allow from 172.17.10.1&#8243; should contain your static IP address if you have one, or that of your client if you are building this site for someone else to access.  Of course, you can add more than one line in that format.  It will allow anyone arriving from an IP in the Allow statement(s) to access the WPAdmin login screen without having the enter the Apache Username/Password combination.  Everyone else will be stopped at the Apache login screen, and if they authenticate there they will then receive the WP login screen.  I do this on over 100 WP sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bobby Kozora</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-110135</link>
		<dc:creator>Bobby Kozora</dc:creator>
		<pubDate>Wed, 18 Nov 2009 15:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-110135</guid>
		<description>I&#039;m trying to use apache authentication as added protection to the password protected admin section of one of my sites. The site&#039;s using Wordpress. What&#039;s happening is when I access the admin section the .htaccess file in that directory isn&#039;t executing. Well, it will throw errors but if all&#039;s fine it passes back to my root .htaccess which then displays the 404 page. If I remove the .htaccess from my admin directory I can once again access my login page. Any ideas? I&#039;m stumped.</description>
		<content:encoded><![CDATA[<p>I&#8217;m trying to use apache authentication as added protection to the password protected admin section of one of my sites. The site&#8217;s using Wordpress. What&#8217;s happening is when I access the admin section the .htaccess file in that directory isn&#8217;t executing. Well, it will throw errors but if all&#8217;s fine it passes back to my root .htaccess which then displays the 404 page. If I remove the .htaccess from my admin directory I can once again access my login page. Any ideas? I&#8217;m stumped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris jar</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-72822</link>
		<dc:creator>chris jar</dc:creator>
		<pubDate>Tue, 05 May 2009 10:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-72822</guid>
		<description>Hi,

I encountered this problem.

I have &lt;code&gt;.htaccess&lt;/code&gt; file:

&lt;pre&gt;AuthType Basic
AuthName &quot;RestrictedFilesmain&quot;
AuthUserFile &quot;d:\Program Files\Apache Group\Apache2\htdocs\main\conf\c.htpasswd&quot;
ErrorDocument 401 &quot;ERROR_ 441 Authorization Required&quot;
ErrorDocument 403 &quot;ERROR_ 403 Forbidden&quot;
ErrorDocument 404 &quot;ERROR_ 404 Not Found&quot;
Require user loggeduser
Require user chris&lt;/pre&gt;

and &lt;code&gt;c.htpasswd&lt;/code&gt; file
&lt;pre&gt;loggeduser:10144831511059024327
chris:a2wssd&lt;/pre&gt;

When I log in into the protected page for the first time I enter chris:a2wssd and I am allowed to enter the page. Next I change password in the &lt;code&gt;c.httpasswd&lt;/code&gt; file into &lt;code&gt;a2ws4ss&lt;/code&gt;. And I still have access to the page just using refresh button in my Firefox browser.

It looks like the Apache server didn&#039;t notice that I have change the password value in the mean time. What&#039;s wrong? I need to stop immediately the access to the protected page by changing the password in the file.

Regards chris</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I encountered this problem.</p>
<p>I have <code>.htaccess</code> file:</p>
<pre>AuthType Basic
AuthName &amp;quot;RestrictedFilesmain&amp;quot;
AuthUserFile &amp;quot;d:\Program Files\Apache Group\Apache2\htdocs\main\conf\c.htpasswd&amp;quot;
ErrorDocument 401 &amp;quot;ERROR_ 441 Authorization Required&amp;quot;
ErrorDocument 403 &amp;quot;ERROR_ 403 Forbidden&amp;quot;
ErrorDocument 404 &amp;quot;ERROR_ 404 Not Found&amp;quot;
Require user loggeduser
Require user chris</pre>
<p>and <code>c.htpasswd</code> file</p>
<pre>loggeduser:10144831511059024327
chris:a2wssd</pre>
<p>When I log in into the protected page for the first time I enter chris:a2wssd and I am allowed to enter the page. Next I change password in the <code>c.httpasswd</code> file into <code>a2ws4ss</code>. And I still have access to the page just using refresh button in my Firefox browser.</p>
<p>It looks like the Apache server didn&#8217;t notice that I have change the password value in the mean time. What&#8217;s wrong? I need to stop immediately the access to the protected page by changing the password in the file.</p>
<p>Regards chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Motosauro</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-65043</link>
		<dc:creator>Motosauro</dc:creator>
		<pubDate>Tue, 17 Feb 2009 09:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-65043</guid>
		<description>Thanks for the snippets, I pasted them into my blog since I tend to forget them very easily :)

Just one question: why do you think it&#039;s better to put ErrorDocument override in .htaccess files rather than vhost definitions?
I place them in vhost definition files because they don&#039;t ever change (almost). I guess it&#039;s just a matter of personal taste though

Thanks mate :)</description>
		<content:encoded><![CDATA[<p>Thanks for the snippets, I pasted them into my blog since I tend to forget them very easily :)</p>
<p>Just one question: why do you think it&#8217;s better to put ErrorDocument override in .htaccess files rather than vhost definitions?<br />
I place them in vhost definition files because they don&#8217;t ever change (almost). I guess it&#8217;s just a matter of personal taste though</p>
<p>Thanks mate :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-44065</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Mon, 11 Aug 2008 17:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-44065</guid>
		<description>&lt;p&gt;&lt;strong&gt;@ Fred&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Absolutely right.  Thanks for the heads, thats a pretty big foul up on my part.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><strong>@ Fred</strong></p>
<p>Absolutely right.  Thanks for the heads, thats a pretty big foul up on my part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-44060</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Mon, 11 Aug 2008 14:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-44060</guid>
		<description>Regarding &quot;Require password for 1 file only&quot;, shouldn&#039;t this:
&lt;pre&gt;AuthName &quot;htaccess password prompt&quot;
AuthType Basic
AuthUserFile /home/askapache.com/.htpasswd
Require valid-user&lt;/pre&gt;

be this:
&lt;pre&gt;AuthName &quot;htaccess password prompt&quot;
AuthType Basic
AuthUserFile /home/askapache.com/.htpasswd
Order deny,allow
Deny from all
Require valid-user&lt;/pre&gt;

Your example allowed anyone on in two of my systems because of lack of a deny clause.  Adding the two lines solved it.</description>
		<content:encoded><![CDATA[<p>Regarding &#8220;Require password for 1 file only&#8221;, shouldn&#8217;t this:</p>
<pre>AuthName &amp;quot;htaccess password prompt&amp;quot;
AuthType Basic
AuthUserFile /home/askapache.com/.htpasswd
Require valid-user</pre>
<p>be this:</p>
<pre>AuthName &amp;quot;htaccess password prompt&amp;quot;
AuthType Basic
AuthUserFile /home/askapache.com/.htpasswd
Order deny,allow
Deny from all
Require valid-user</pre>
<p>Your example allowed anyone on in two of my systems because of lack of a deny clause.  Adding the two lines solved it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lauren</title>
		<link>http://www.askapache.com/htaccess/apache-authentication-in-htaccess.html#comment-37576</link>
		<dc:creator>Lauren</dc:creator>
		<pubDate>Tue, 25 Mar 2008 23:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/apache-authentication-in-htaccess.html#comment-37576</guid>
		<description>I deactivated the plugin, tried to modify the .htaccess in wp-admin, but still cannot get into my admin panel. Help!!!!!!</description>
		<content:encoded><![CDATA[<p>I deactivated the plugin, tried to modify the .htaccess in wp-admin, but still cannot get into my admin panel. Help!!!!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
