Issues with BulletProof Security plugin - solutions

[nfable]

Not really a bug on the PPress end, but wanted to potentially save others hours of head banging.
I've gone back and forth with the developer of BulletProof Security who has been very helpful in combing over this with me.  His site is here: http://www.ait-pro.com/aitpro-blog/2252/bulletproof-security-plugin-support/checking-plugin-compatibility-with-bps-plugin-testing-to-do-list/comment-page-1/#comment-6267


The issue: file will not verify.  Verification fails when creating a post.  Error 404 even though file is on the same server as you wp install.

Dev recommended adding the following to .htaccess:

Code: [Select]

# Blubrry PowerPress 404 / 403 redirection fix
# You can change the made up directory name "bpp" to any other name you want /media/ or /podcast/ etc but you
# must have something here. You cannot redirect back to your root folder or BPP will hang
RewriteCond %{QUERY_STRING} powerpress_pinw=(.*) [NC]
RewriteRule (.*) /bpp/$1 [R=301,L]
The 'bpp' directory he suggests he called a 'virtual directory' but it is not in the sense of server-side directories, he just meant 'a directory name that does not exist', I would call that a phantom directory, but I 'm no dev

This worked on his end, but mine was still fudged up.  I went through my .htaccess and when I omitted code that his plugin (BulletProof Security) requires in the .htaccess, all things work again.

Code: [Select]

# FILTER REQUEST METHODS
RewriteCond %{REQUEST_METHOD} ^(HEAD|TRACE|DELETE|TRACK) [NC]
RewriteRule ^(.*)$ - [F,L]
However,  you can still post with the code above remaining in the .htaccess ... but there's a trick.  If you create a post and attach a podcast BUT DO NOT VERIFY OR PREVIEW then you can just click 'publish' and all will be good.  I received a '404' when submitting to publish, then directly under it there was a message 'Post successful' ? 

So hopefully others can find solace in here; end the end the dev thinks it may be a caching issue and as I use W3 Total Cache, he may be right but my work around is good enough to keep me 'casting for now.

best,
nf

[mgdell]

Thanks for posting this!  I'm sure there will be people that search and find your solution.

-Mike

[angelo]

If you are going to dig this deep, perhaps you would consider getting your own dedicated/virtual dedicated server and setup real caching and PHP acceleration using tools like eAccelerator, APC or even Zend's products. If you do things correctly, it will out perform any PHP developed caching solution by magnitudes.

BTW most well maintained web hosting providers already install accelerators and caching methods like APC, which makes these PHP caching solutions just another layer in the web serving process.