• First of all i want to say thank you for this plugin. The concept is great and the way it works also.
    However with wp 3.2.1 i randomly get while using FlexiCache, firefox saying “The browser has stopped trying to retrieve the requested item. The site is redirecting the request in a way that will never complete.” If i am looking at the activity behind with firebug or live headers plugin or in IE with the developer tools i see my index is looping into a 302 redirect. I get about 25 – 30 redirects until the browser stops and spits out the message. Initially i thought it is from my Varnish cache in front of nginx but it continues even after i left nginx to serve the pages without caching. So i disabled all the plugins and started to test them one by one until i enabled flexicache and after about 3 or 4 hours it started again. Only the index is doing this. If i try to access various pages in the site it works just fine. So now i have 3 days since i disabled flexicache and i got no error whatsoever.
    Thank you for your time.

    Regards
    Andy

    http://wordpress.org/extend/plugins/flexicache/

Viewing 1 replies (of 1 total)
  • Plugin Author simon.holliday

    (@simonholliday)

    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.

Viewing 1 replies (of 1 total)
  • The topic ‘[Plugin: FlexiCache] wp 3.2.1 issues’ is closed to new replies.