----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files.  Don't make us guess your problem!!!
----------------------------------------------------------------

I ran into the same problem.  The solution is to send a META EXPIRE tag as part of the 
document.  Note that using the API to set the expiration date in the header does not 
always work! Some braindead browsers (read IE) ignore it.  Try this:

<meta http-equiv="Pragma" content="no_cache">
<meta http-equiv="EXPIRES" content="Tue, 14 Dec 1999 10:04:37 GMT">

I am not familiar with the Pragma sub-tag and haven't traced down which one of these 
lines work,  but they do!  Another thing I have done is to create a getLastModified() 
method in my servlets.  It just returns the current time so that it always looks 
modified.  Not the best solution.  But there is not enough state in
the database to which I am connecting to detect *what* might have changed.  So I just 
always assume that something has changed (at least for now).

The output of the getLastModified() method gets fed into the meta EXPIRES tag above.  
So when I do make getLastModified() more intelligent,  the benefit will be passed onto 
the meta EXPIRES tag generation code.

Hope this helps.
Kevin

>
> Michael Travars wrote:
> >
> >
> > Hey all...
> >   I've got another problem.  I'm writing a web application that uses
> > multiple servlets, and there are instances where I want to run one servlet,
> > run another servlet, then run the first servlet again (with the output
> > changing based upon the output from the second servlet, if that makes
> > sense).  The problem I seem to be having is that my servlets don't refresh..
> > That is, clicking on the link for the servlet brings up the same page that
> > it did before running the second one.  My question is, is there a way to
> > force the server to go through the complete servlet every time, rather than
> > using the cached pages?  I still need the pages to be cached so users can go
> > back to them.
> > Help!!!
> > Thanks
> > mike



--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to