Topic: Regarding cache headers
I've noticed that several recent BB releases (including punBB) are setting a series of no-cache headers. For punBB these are set in headers.php and consist of:
header('Cache-Control: no-store, no-cache, must-revalidate'); header('Cache-Control: post-check=0, pre-check=0', false); header('Last-Modified: '.gmdate('D, d M Y H:i:s').' GMT'); header('Expires: Thu, 21 Jul 1977 07:30:00 GMT'); header('Pragma: no-cache');
The result is that when using the "Back" or "Forward" functions in a web browser, the browser will re-fetch a page from the web rather than load it from cache. I realize that this is personal preference, but for me this is a PITA. I'm on either a low-bandwidth dialup or a high-latency satellite connection, and this re-fetching make navigating a BB really slow. (VB3, with it's many graphics, is a particular nightmare.)
I've experimented a bit with these no-cache headers and found that just one of them causing this re-fetching on Back or Forward. I've disabled it on my punBB at http://www.labradorstraits.net/forum/ :
//header('Cache-Control: no-store, no-cache, must-revalidate');
The purpose of no-cache headers is to ensure that the reader sees most recent content. However, I would argue that re-fetching a page on Back or Forward is wrong, as that is not the intent of these functions. When I hit "Back" I want to go back to exactly what I was looking at previously, not "back" to a now-revised copy of that page.
New post markers and cookie updating work just fine on my board with the above cache header disabled. And I can flip back and forth between pages without re-fetching from the web each time.
I'd be interested to hear any comments others may have on this.