Announcement

Collapse
No announcement yet.

Need to refresh/F5 to show updates in 3.8.2

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Need to refresh/F5 to show updates in 3.8.2

    Hi - I've just installed a brand new install of vbulletin (3.8.2) and have a problem displaying updated content.

    After doing something that adds new dynamic content (like adding a new post) and going back to a page that has already been viewed, the old page is loaded from cache and not the updated one. I can click around and constantly get the old content until I force the refresh of the page. I can replicate the problem myself and I have had about a dozen users of my site experiencing the same problem.

    I can replicate the problem on my production web server as well as on my development server, both running on centos/apache2.2.3 and running php5.2.9 and 5.1.6 respectively. It makes no difference whether it's running with my plugins enabled (vbadvanced/passive video/usergroup as mod) or whether I disable them all (including setting DISABLE_HOOKS to true in config.php).

    I've also check to ensure I can replicate using the standard theme, and in fact after selecting the standard theme I had to hit refresh to stop it rendering the old page/theme because of the problem. Have tried IE and Firefox and it happens in both, have ensured I've flushed cache/cookies/etc.

    The only way I can stop the problem is to force "Add No-Cache HTTP Headers" to ON. This fixes the refresh problem, but increases the page serving going on and is contrary to almost every optimisation recommendation ever made for vbulletin.

    I've seen a lot of threads describing this exact same problem with 3.8.2 but no solutions. Surely forcing no-cache on isn't seen as a reasonable solution.

    Given that I can replicate this using different browsers, different physical machines, different versions of PHP, and using a brand new install of vbulletin with hooks turned off and the standard theme, it seems a problem that is definitely related to vbulletin.

    Any thoughts?

  • #2
    Normally I recommend adjusting the cache settings in your browser and/or enabling that no-cache option. If there is a problem with the site itself then it would likely be your web server. Maybe there is a problem with the http headers. But I don't have any experience with that. The people in the server forum might be able to make some recommendations:

    http://www.vbulletin.com/forum/forumdisplay.php?f=14

    Comment


    • #3
      Thanks Jake - I can replicate the same problem on two different servers (one running prod from my host, one running under vmware in my own dev environment), so its not one box, but it could be a common configuration as they are both running the CentOS redhat derivative.

      I'll cross post and see if I get any more responses.

      Comment


      • #4
        Oh well, I tried posting in the server forum and one of your ever helpful "customer service" representatives told me off for cross posting and closed the post. I must say its not the sort of customer service I would expect given that I'm supposed to be incented to actually pay renewals every year.

        So I'm guessing nobody has much of an idea then?

        Comment


        • #5
          Is the no-cache header option on or off?

          Comment


          • #6
            No-cache is currently set to true, and this does alleviate the problem. However, every tuning guide I've found recommends this is always at the default of false. As a result there will be a lot more html reloading going on of course.

            Is there a way of effectively diagnosing the problem by looking at the (semi) raw http stream? I can dump the actual http content with the relevant headers easily enough if that would lead to a series of tests and/or conclusions...

            Comment


            • #7
              getting IE's live http headers, or Firefoxes would likely help.

              Comment


              • #8
                Originally posted by nmilne View Post
                No-cache is currently set to true, and this does alleviate the problem. However, every tuning guide I've found recommends this is always at the default of false. As a result there will be a lot more html reloading going on of course.

                Is there a way of effectively diagnosing the problem by looking at the (semi) raw http stream? I can dump the actual http content with the relevant headers easily enough if that would lead to a series of tests and/or conclusions...
                Interestingly, I came accross this thread because I WAS having trouble posting new messages. The site would just sit and spin.....even though the message would post immediately, confirmed by opening up a new tab.

                I could not find a solution, until I saw your post (Thank you!). My no-cache was set to on/true - I turned it off. Problem went away.

                Are you running XCache or similar?

                J

                Comment

                widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                Working...
                X