<?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"
	>
<channel>
	<title>Comments on: Update: AskApache Password Protect Plugin</title>
	<atom:link href="http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html</link>
	<description>Web Development</description>
	<pubDate>Sat, 30 Aug 2008 04:42:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Robert</title>
		<link>http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-43298</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 17 Jul 2008 16:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-43298</guid>
		<description>@ Ivan. After having installed the plugin, I couldn't use the Windows Live Writer any longer. All I got was a "403 forbidden" error. Then I played around with activating and deactivating the security modules in the plugin configuration. Now I know at least one thing for sure: The module "1022 BAD Content Type Denies any POST request with a content type other than application/x-www-form-urlencoded&#124;multipart/form-data" blocks WLW. I deactivated it - now WLW has access to my blog again.</description>
		<content:encoded><![CDATA[<p>@ Ivan. After having installed the plugin, I couldn&#8217;t use the Windows Live Writer any longer. All I got was a &#8220;403 forbidden&#8221; error. Then I played around with activating and deactivating the security modules in the plugin configuration. Now I know at least one thing for sure: The module &#8220;1022 BAD Content Type Denies any POST request with a content type other than application/x-www-form-urlencoded|multipart/form-data&#8221; blocks WLW. I deactivated it - now WLW has access to my blog again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Beckett</title>
		<link>http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-42592</link>
		<dc:creator>Brad Beckett</dc:creator>
		<pubDate>Wed, 25 Jun 2008 10:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-42592</guid>
		<description>I figured it out... you have to FTP in and make sure all your .htaccess files in your mail /public_html/wp-admin/ is CHMOD 755 and /public_html/.htpasswda1 file is also CHMOD 755

Works for me!</description>
		<content:encoded><![CDATA[<p>I figured it out&#8230; you have to FTP in and make sure all your .htaccess files in your mail /public_html/wp-admin/ is CHMOD 755 and /public_html/.htpasswda1 file is also CHMOD 755</p>
<p>Works for me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: highhopesgardens</title>
		<link>http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-40854</link>
		<dc:creator>highhopesgardens</dc:creator>
		<pubDate>Fri, 16 May 2008 02:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-40854</guid>
		<description>I added the askapache password plugin to my 2.5.2 wordpress blog hosted on Yahoo (never found any warnings in install documentation on Wordpress against this) and now I cannot access my dashboard to remove the plugin (or do anything else on my blog).  There are not any .htaccess files or password files that I can see in Yahoo file manager or filezilla.  After I installed it and gave user name and password, the first login, it refuses my username and password and I'm locked out of my own blog.  How can I fix this, short of blowing everything away and reinstalling Wordpress and my backups?</description>
		<content:encoded><![CDATA[<p>I added the askapache password plugin to my 2.5.2 wordpress blog hosted on Yahoo (never found any warnings in install documentation on Wordpress against this) and now I cannot access my dashboard to remove the plugin (or do anything else on my blog).  There are not any .htaccess files or password files that I can see in Yahoo file manager or filezilla.  After I installed it and gave user name and password, the first login, it refuses my username and password and I&#8217;m locked out of my own blog.  How can I fix this, short of blowing everything away and reinstalling Wordpress and my backups?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lauren</title>
		<link>http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-37575</link>
		<dc:creator>Lauren</dc:creator>
		<pubDate>Tue, 25 Mar 2008 23:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-37575</guid>
		<description>I installed your password plugin, not cannot get into admin panel. Did all you suggested, but cannot bring up admin... what did I do wrong? 
thanks
lauren</description>
		<content:encoded><![CDATA[<p>I installed your password plugin, not cannot get into admin panel. Did all you suggested, but cannot bring up admin&#8230; what did I do wrong?<br />
thanks<br />
lauren</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andi</title>
		<link>http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-37020</link>
		<dc:creator>Andi</dc:creator>
		<pubDate>Sun, 09 Mar 2008 19:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-37020</guid>
		<description>I get the error

&lt;pre&gt;&lt;br /&gt;
Warning: Wrong parameter count for sha1() in /public_html/sitename/wp-content/plugins/askapache-password-protect.php on line 532&lt;br /&gt;
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>I get the error</p>
<pre>
Warning: Wrong parameter count for sha1() in /public_html/sitename/wp-content/plugins/askapache-password-protect.php on line 532
</pre>
]]></content:encoded>
	</item>
	<item>
		<title>By: norvo</title>
		<link>http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-36487</link>
		<dc:creator>norvo</dc:creator>
		<pubDate>Sat, 01 Mar 2008 23:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/wordpress-plugins/securing-htaccess-plugin.html#comment-36487</guid>
		<description>hi, great idea for a plugin. however, like a lot of the others i read in the comments, i also get a 404 page and can not access the wp-admin directory. nor does it prompt me for a username or password. any fix for this?

it would also be great if you could add something like this to the .htaccess file in the root of the blog directory (seperate from the other wordpress variables:

&lt;code&gt;&lt;br /&gt;
&#160;&lt;br /&gt;
Options All -Indexes&lt;br /&gt;
&#160;&lt;br /&gt;
RewriteEngine On&lt;br /&gt;
RewriteBase /&lt;br /&gt;
RewriteCond %{THE_REQUEST} /(wp-includes&#124;wp-content)/.*\ HTTP/&lt;br /&gt;
RewriteCond %{HTTP_REFERER} !^http://(www\.)yourdomain\.com/.*$ [NC]&lt;br /&gt;
RewriteRule .* - [F]&lt;br /&gt;
&#160;&lt;br /&gt;
&lt;/code&gt;

this would exclude people for browsing or direct calling the plugins or template stuff except for the blog software itself. just a thought :)</description>
		<content:encoded><![CDATA[<p>hi, great idea for a plugin. however, like a lot of the others i read in the comments, i also get a 404 page and can not access the wp-admin directory. nor does it prompt me for a username or password. any fix for this?</p>
<p>it would also be great if you could add something like this to the .htaccess file in the root of the blog directory (seperate from the other wordpress variables:</p>
<p><code><br />
&nbsp;<br />
Options All -Indexes<br />
&nbsp;<br />
RewriteEngine On<br />
RewriteBase /<br />
RewriteCond %{THE_REQUEST} /(wp-includes|wp-content)/.*\ HTTP/<br />
RewriteCond %{HTTP_REFERER} !^http://(www\.)yourdomain\.com/.*$ [NC]<br />
RewriteRule .* - [F]<br />
&nbsp;<br />
</code></p>
<p>this would exclude people for browsing or direct calling the plugins or template stuff except for the blog software itself. just a thought :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
