Jump to content

"Print HTTP no-cache headers" disabled causes problems


Recommended Posts

Posted

Hello,

I would like to use caching on my forum. To accomplish this, I disabled the "Print HTTP no-cache headers" feature. However, when I did that, it caused all kinds of weird bugs/glitches on my forum.

One such bug being that, when I reply to a topic, go back to the board (via logo link), then click that topic again, my post does not show up. I must refresh the page manually for me to see it. I isolated it to this setting, because when it is enabled, everything works perfectly.

Could you guys explain to me why it does this, or help me to solve it?

Thanks!

BTW, I asked IPS to help, and they said to post here -_-

Posted

The browser assumes it's fine to cache the entire webpage and doesn't pull the data from the webserver, but from its own cache instead.
I guess it could be fixed by adding the time of the last post/update of a topic in headers.

Posted

The browser assumes it's fine to cache the entire webpage and doesn't pull the data from the webserver, but from its own cache instead.
I guess it could be fixed by adding the time of the last post/update of a topic in headers.

Hello,

Is there any way I could do that?

Posted

are you using any tools like APC cache or Varnish/Nginx?

I'm currently using Cloudflare. From what I understand though, cloudflare's caching is useless with print no-cache headers.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...