Now being served - Stale CR4 Pages.

No, CowAnon, it's not because we want contributors to post and move on. Stay as long as you like and "eat" as much as you want (to borrow a verb from your analogy).

I'm unable to get an answer to your question today (it's a Sunday), but will bring this to the attention of our technial gurus tomorrow morning (Monday). I'm not anxious to call this a "bug", but it sure as heck isn't a conspiracy to keep anyone away.

- Moose

Thanks for your help, Moose. I'm not given to conspiracy "theory," so that was not what I meant when joking about moving on (to another topic)...about partaking but not tarrying. My theory was that, assuming a post-er had just read and reviewed what s/he posted as well at that which the posted message was responding to, then the CR4 service might, somehow, be deemed by its operators to work more efficiently without updating a requested page that the post-er had just left—something like rationing of server resources in order to enhance (i.e., speed up &or lessen choke points in) message traffic throughput for all.

Anyway...looking forward to what the CR4 technical gurus have to say. Again, thank you.

CA

PS: It would not be the first bug I ever ate. How about you?

I am not able to reproduce what you are describing but it really sounds like a browser caching issue... the page you are going "back" has the same url as the the page you viewed originally, so your browser may be throwing the older content up. Check your browser's cache settings to see if it is "always checking" for new content.

Thanks
- Mark