Reloading pages?

[Deltanugz]

I notice that I have to manually reload the main page when I back out of a thread if I want to see the latest updated version. Otherwise I just see the cached version in my browser, which could be hours old. Is this an easy fix?

[Roscoe]

I think that is normal behviour, Delta. You could look thru the options in your browser and find the section that deals with loading pages from cache. Then set it to always reload from the server. I know firefox always does this in v1 but the behaviour was changed in v1.5 to keep a memory cache of previously view pages so they load faster. Of course it's configurable.
I hit the 'R' key in Opera to reload to see the new posts myself.

[Deltanugz]

The thing is that other forums I check don't have the same behavior when using the same browser (Camino). When I back out of a thread, the forum listings page should show no new posts on the thread I just read, without me having to reload the page manually.

I believe there is a way to configure web pages to tell the browser to not rely on the cached version. This should be implemented for all forum listings pages, if not the whole site.

[Roscoe]

Maybe someone can correct me if I'm wrong, but I believe it is the function of the browser (client) about how to handle reloads from the web server. IOW, your browser is responsible for requesting a reload. The server doesn't push, the browser pulls.
Do you use Camino exclusively? Have you tried Firefox?

[Deltanugz]

I'm seeing the same behavior in Safari.

I agree with your point, but I think that the server can tell the browser "My content changes all the time, you should request a fresh version of me each time this page is accessed."

[Roscoe]

Ahhh...a Mac user....much love.:D

I don't think the server can do that. You have to request a page from the server either manually (with reload button) or by setting your browser behaviour to always check for a new page when you hit the back button (like firefox v1).
Maybe c-ray can enlighten me if I'm wrong.

[c-ray]

pages shouldn't reload with a simple step back
at least in my experience

[Deltanugz]

Just saying that other forums that I post at definitely DO reload with a simple step back. Go try it over at icmag.com:

While logged in and viewing a forum, note the pot leaf in green signifying that there are new posts in that thread. Click on the thread and view all the posts in it. Then click the back button. The forum page will reload, and the little pot leaf by the thread you viewed will turn blue-green, signifying that the thread you just viewed has no new posts since you last viewed it.

I don't think that every page need to be set up to reload with a simple back click, as that would be a waste of server bandwidth, but the forum pages should do so.

BTW thanks for all your hard work c-ray, the site looks great and shows lots of promise. I hope you know how much we all appreciate it :)

[Deltanugz]

If I were to set up a simple html page that I did not want the browser to cache, I would use the following tag:

<**** ***********="Pragma" CONTENT="no-cache">

This tag tells the browser that it should not cache the page, and instead it should reload the page from the server.

A quick look over the vbulletin documentation lead me to the following page:

http://www.vbulletin.com/docs/html/vboptions_group_http

Scroll down about half-way and you'll see the bullet item "Add No-Cache HTTP Headers."

Not that I know much about HTML or vbulletin, but I think this may be the option that we're discussing.

[c-ray]

thanks I'll look into it

[Deltanugz]

bump

[mace]

Don't confuse (****)tags and HTTP headers ;)

tags are HTML, headers are HTTP, the first you use in the pages themselves, the latter you have to set at the Webserver/app directly, its more reliable than the tags.

peace,

mace

[hash]

Hello,

Yes, your right ... it is up to the browser for its caching behaviors ... but, it can be handled by some header tags and or javascript and or php in the code of the webpage. This does depend on if the browser can or wants to follow these instructions.

You can also set most browsers to check for a new page every visit as well.... this way every time you click 'back' on any website, it will check for a new version of the page off of the server. Generly, most browsers default to caching for quickness and bandwith.

I am sure we can add some code to the site to handle this request.
Have to dig through my black book ... its been a while for that code ... but i know I have it!

Hash

Maybe someone can correct me if I'm wrong, but I believe it is the function of the browser (client) about how to handle reloads from the web server. IOW, your browser is responsible for requesting a reload. The server doesn't push, the browser pulls.
Do you use Camino exclusively? Have you tried Firefox?

[hash]

Thanks man ... that's the one!!
You saved a ton of searching ;)



If I were to set up a simple html page that I did not want the browser to cache, I would use the following tag:

<**** ***********="Pragma" CONTENT="no-cache">

This tag tells the browser that it should not cache the page, and instead it should reload the page from the server.

A quick look over the vbulletin documentation lead me to the following page:

http://www.vbulletin.com/docs/html/vboptions_group_http

Scroll down about half-way and you'll see the bullet item "Add No-Cache HTTP Headers."

Not that I know much about HTML or vbulletin, but I think this may be the option that we're discussing.

[hash]

you know your stuff ;)

Don't confuse (****)tags and HTTP headers ;)

tags are HTML, headers are HTTP, the first you use in the pages themselves, the latter you have to set at the Webserver/app directly, its more reliable than the tags.

peace,

mace

[hash]

Again ... thanks for the link ....

DONE :D

If I were to set up a simple html page that I did not want the browser to cache, I would use the following tag:

<**** ***********="Pragma" CONTENT="no-cache">

This tag tells the browser that it should not cache the page, and instead it should reload the page from the server.

A quick look over the vbulletin documentation lead me to the following page:

http://www.vbulletin.com/docs/html/vboptions_group_http

Scroll down about half-way and you'll see the bullet item "Add No-Cache HTTP Headers."

Not that I know much about HTML or vbulletin, but I think this may be the option that we're discussing.

[Deltanugz]

SSWWEEEEETTTTTT!!!

Hash you rule. That's been bugging the shit out of me for days now.

[mace]

I dito Deltanugz!