simon.holliday

Hi,

Sorry for the slow reply. I don’t seem to get any notifications when people post here.

There are no redirects used anywhere in the plugin, so I’m confident that this is not directly a problem with the plugin.

It is likely that something elsewhere in your site is causing a page to redirect to itself, and then FlexiCache is caching that redirect header, which means it will send it again every time the page is loaded, until the cache expires.

If this is something which is widespread I will need to address it, but so far this is the only report, and without knowing which circumstances cause the initial redirect, and whether that redirect is in the WordPress core code or not, there isn’t really much I can do to help.

Si.

Thanks for the update. I haven’t looked at the multisite stuff much since WordPress MU – that ms-files.php process looks like a really inefficient way of serving static files.

WP Super Cache and FlexiCache work very differently and I can see how in this particular situation WP Super Cache handles it without modification.

What I would suggest trying as a temporary workaround for your own site is to remove the additional RewriteRule you added above, and instead add the following at the top of your .htaccess file:

# BEGIN Temp Multisite Workaround
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} www\.mapped_domain\.com$
RewriteRule ^files/(.+)$ /wp-content/blogs.dir/2/files/$1 [L]
</IfModule>
# END Temp Multisite Workaround

Note that I have written this to match your original example, so you will need to edit the domain name and paths appropriately. This should do the same as ms-files.php is doing, but without using any PHP.

Please note that although I have tested the rules above locally, it’s not been tested thoroughly as I would with a plugin release, so you should consider it a temporary and experimental work-around only!

Si.

Hi there,

Thanks for the feedback.

It looks like I might just be able to add an exception to the standalone .htaccess rules which exclude any URLs beginning with “/files/” from being intercepted, but I’ll do a bit of reading and testing to see what other issues there might be.

I’ll post here again when I’ve got a solution!

Si.

Hello, FlexiCache hasn’t been tested with WordPress 3.1.1 yet, and as such it’s only marked as being compatible up to version 3.1.0.

From your brief description, it doesn’t sound like your problem is being caused by FlexiCache, as the plugin won’t affect what you see when logged in as an admin – but if you can give me a repeatable example I can test with, and let me know what other plugins you have installed, I will have a look when I test with WordPress 3.1.1.

Si.