This message applies primarily to frequent visitors to the TullyRunners.com web-site (TullyRunners with a "s")...

A number of visitors (including myself when I check updates), are NOT getting updated web-pages from the web-server when web-pages are being updated frequently (such as on the weekends when new results are being added frequently)...

Currently ... the best (and only way for visitors experiencing this problem) is to do a page REFRESH....  Not everybody is experiencing this problem (but as I noted, it is happening to me).

To REFRESH a page in Internet Explorer ... Press the button shown below:

OR ... Press the F5 key .... F5 does the same thing as pressing the button.

To REFRESH a page in Mozilla Firefox ... Press the button shown below:

OR ... Press the F5 key .... F5 does the same thing as pressing the button.

NOTE ... this problem does NOT seem to effect my back-up site at:  http://www.tullyrunner.com/  (no "s" on tullyrunner) ... I am currently updating this back-up site at the same time as I update the main web-site ... It is a smaller web-site with limited disk space (so the older material is not available there), but it works fine for the current material.

Why is this Refresh Problem Occurring on TullyRunners??

TullyRunners is hosted on a commercial web-hosting site (Web.com ... which one of the largest web-hosting companies in the US ... it was formerly known as  Interland) ... Late last fall, Web.com relocated TullyRunners from a small group web-server to a much larger web-server "farm" comprised of multiple thousands of commercial web-sites ... For me, this stabilized the monthly cost while increasing allowable disk space, transfer volume and bandwidth (and that's great).

BUT I soon discovered the web-page "Refresh" problem (updated pages not being captured by the web browser in a timely manner) ... Tech support at Web.com confirmed the problem ... HOWEVER, some current large commercial web-hosters view this as a "feature", and not a problem ... a top person in the Web.com IT department responded to my complaints with "That's the way it is!!".

So for the time being ... Viewers experiencing the problem on TullyRunners.com will sometimes need to manually Refresh web-pages  ... Infrequent viewers will not experience this problem.

Why does it happen?

This section is boring details for viewers interested in web-hosts, browsers and HTML code ... TullyRunners on Web.com is one of multiple web-sites on the web-server "farm" (literally hundreds-to-thousands of networked computers) ... the Refresh "feature" is based on how modern web-servers and browsers communicate with each other ... I discovered that current web-browsers and web-servers may (and sometimes do) ignore older HTML code used to force a web-server to send the most recent web-page directly from the server to the browser (HTML code is used to make web-pages)...

The underlying problem involves separate "caches" used by the browser and by the web-server ... if a web-page is in a cache (stored memory), it can be retrieved much faster because it has already been downloaded ... Supposedly, a browser and server are suppose to use the most recent web-page - BUT with some web-server farms (due to enormous volume and demand plus intentionally ignoring some older HTML code), cached web-pages are sent to the browser until the cache recycles .... 99% of the time, the browser Refresh button can over-ride the browser & server caches, and retrieve to newest web-page directly from the server.

In Internet Explorer: ... Even setting the "Check for newer versions of stored pages" - "Every time I visit the weppage" ... Does NOT work with these web-server farms (they ignore the browser) ... the Refresh button can over-rides this.

In Internet Explorer 7 ... if I manually deleted all the Temporary Internet files from the browser cache, this would usually cause the most recent web-page to be retrieved directly from the server .... In the new Internet Explorer 8, this no longer works (but Refresh button does work).

I have tested various javascripts to force a direct page Refresh, but I do not like the result....

That's the way things are for the time being.