Howdy:
On 08/22/2000 00:44 USA PT (-0800), micheal@xxxxxxxx ( Michael O Shea ),
wrote...
>Why ?
Below my signature is a note from the WebTen FAQs concerning some
problems with viewing recently changed pages.
Hope that helps.
Glenn
===========
Question: I regularly update documents on the web server, but the updates
never seem to appear. What's wrong?
Answer: It is important to understand how caching works on a web server,
and in a web browser. Here is a hypothetical scenario that will explain
the issue:
WebTen is operating under normal conditions and a commonly-accessed page
is located in the Squid cache. A browser requests this page and it is
transmitted by Squid without checking to see if the page has updated.
This is where WebTen's speed comes from. Now, if a browser "Reload"
request is given by the browser to Squid, Squid will check to see if the
page has updated and it will serve the latest copy. If a "Super-reload"
request is given to Squid it will serve the page from disk no matter what.
Squid keeps commonly-accessed pages in its cache for three days. Once
this time has expired, Squid automatically dumps the contents of its
cache and commonly-accessed pages are stored in cache as they are
accessed.
Netscape has an option entitled "Page in cache is compared to page on
Network". The options for this feature are: "Once per session", "Every
time", and "Never". If Netscape is set to "Never", it will never ask
Squid if the page is updated! If the option is set to "Once per session",
Netscape will ask once if the page has been updated, and if the option is
set to "Every time", Netscape will always ask Squid if it has the latest
document. Tenon recommends that you set your Netscape settings to verify
documents "Every time". This gives you the maximum "Reload"
functionality. To force Netscape to do a "Super-reload", simply hold down
the "option" key while clicking "Reload" on Macintosh systems, and hold
down the shift key while clicking "Reload" on all other platforms.
Unfortunately, Internet Explorer does not have the cache options that
Netscape does. The best IE can do is a "normal" reload which is initiated
by holding down the shift key and clicking the reload button. Numerous
users have encountered problems with IE because it rarely (sometimes
never) checks to see if the page on the network has changed and will only
serve up documents out of its cache. Until Internet Explorer handles
caching properly, we strongly recommend against using IE for web-page
verification.
----
Tenon Intersystems' iTools Mailing List
To unsubscribe: send mail to itools-request@xxxxxxxxx
with the subject: unsubscribe
|
