Working with .htaccess files

[jeckert]

Hi,

Did a deactivate/reactivate. No change.

Did an uninstall/reinstall. No change.

I'm 99.9% certain that this is an issue with the HTTP_REFERER that our authorization plugin requires. I am prepared to whitelist anything that your program uses. However, I'm unsure how to do that.

I can force the following error by attempting to use <DirectoryMatch> like I am <FileMatch>

DirectoryMatch in .htaccess:

Quote:<DirectoryMatch "(/wordpress/wp-content/plugins/featurific-for-wordpress)$">
Satisfy Any
Order allow,deny
Allow from all
Deny from none
</DirectoryMatch>

Error produced:

Quote:Warning: file_get_contents(http://XXX/wordpress/wp-content/uploads/2010/09/myj-Custom1.jpg) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 500 Internal Server Error in /XXX/wordpress/wp-content/plugins/featurific-for-wordpress/featurific.php on line 2132

Warning: file_get_contents(http://XXX/wordpress/wp-content/uploads/2010/06/RapidRide1.jpg) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 500 Internal Server Error in XXX/wordpress/wp-content/plugins/featurific-for-wordpress/featurific.php on line 2132

Warning: file_get_contents(file:///C:/DOCUME%7E1/Admin/LOCALS%7E1/Temp/moz-screenshot.png) [function.file-get-contents]: failed to open stream: No such file or directory in XXX/wordpress/wp-content/plugins/featurific-for-wordpress/featurific.php on line 2132

I'm assuming that I've borked the .htaccess file in this example which forces the error return. Removing the <DirectoryMatch> line returns things back to normal.

I think I need the Apache command to whitelist either the directory, or whatever file uses "file_get_contents".

Adding featurific.php to the <FilesMatch> appears to not remedy the problem.

In searching through the PHP, here's 2130-2132:

Quote://If the image is on a different domain, we can't access it from Flash 9 directly, so we've got to load it by proxy (save locally via PHP).
else {
$image_data = file_get_contents($image);

This confuses me though -- I've got the *exact same* redirect on site #2, which appears in my .htaccess thus:

Quote:# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /XXX/wordpress/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /XXX/wordpress/index.php [L]
</IfModule>

# END WordPress

Given that the redirect is identical in both cases and is only giving me grief in one of the cases, I'm siding with the HTTP_REFERER issue, but I'm pretty wet behind the ears at this sort of thing. Admittedly, from the error it's giving us, it could be an issue with the redirect....but I'm not really sure.