Often you need to do a shift-reload (Hold the shift key down while
clicking reload).  If this fixes the problem, then you should set the
expiration date on the page to something in the past.  (Check the
archives for examples.)

   You should also note that if the clock on the person's computer is
off by a good amount, this can throw most caching schemes off.

Christian Bollmeyer (GMX) wrote:

Am Donnerstag, 23. Januar 2003 17:51 schrieb KEITH KOSMICKI:

Could be I don't understand everything right, but browser history
and browser caches are two different things. The 'history' may
load a page from the cache if the page was cached, or
request a new page from the server if the page isn't in
the cache. Dynamic pages normally shouldn't be
cached. Such caching may be performed on the client, a
possible proxy in-between and finally the server itself.
Ruling out the server on this occasion, you have to tell
the proxy | browser cache that it shouldn't store the
pages in question, but request a fresh version each time,
may it be going back in the history or not. The 'history'
is just a list of URLs and has nothing to do with where
the content displayed finally is loaded from. If this is
your problem, first try to go back in the history and
hit the browser's 'reload' button. This should force
the browser to reload a fresh page regardless of the
browser cache. Check if the application displays the
correct values, afterwards. If it does, your pages are
missing some header info to avoid caching. I already
posted the details on this issue on 9th of January,
with an additional follow-up by Adrian Janssen. The
topic was 'location.href'; you might want to check
out the list archives for possible solutions if this
proves to be your problem as well.

HTH,

-- Chris (SCPJ2)




A user has indicated that even though a new item was added to a particular
area, the list would not reflect that when going back to that screen.

Those lists are application lists that only change if the administrator
makes a change to that list in the table.  There is code there to set that
application(whatever) = "" but for some reason it is pulling the history
page rather than opening a refreshed page.

Is there a way to pull a fresh page from the web server rather than reload
a page out of history?


TIA,


Keith E. Kosmicki
Applications Consultant
State of IL Human Services
STL Technology Partners


=========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".

Some relevant archives, FAQs and Forums on JSPs can be found at:

http://java.sun.com/products/jsp
http://archives.java.sun.com/jsp-interest.html
http://forums.java.sun.com
http://www.jspinsider.com


===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".

Some relevant archives, FAQs and Forums on JSPs can be found at:

http://java.sun.com/products/jsp
http://archives.java.sun.com/jsp-interest.html
http://forums.java.sun.com
http://www.jspinsider.com

Reply via email to