In looking over the HTTP/1.1 spec, the header to set is 'Last-Modified'. In
the spec documentation, though, they state that there's 60 seconds of slop
allowed, in the event that the browser and server clocks are out of sync.
Still, they say that if the cached copy differs from the server copy by that
amount, the client must treat the cached copy as stale and reload it. Now,
as to whether IE abides by these rules or not...
Setting it in the JSP may be as simple as
'response.setHeader("Last-Modified",
java.util.Calendar.getInstance().getTime())', although you may need to
represent the time in ISO-9601 notation ('Wed, 15 Nov 1995 04:58:08 GMT').
Hope this helps.
- Roby
Joe Laffey wrote:
> On Tue, 13 Mar 2001, Zsolt Koppany wrote:
>
> > No, there is no proxy, everything runs in a simple LAN.
>
> You can also try adding the following at the top of your HTML document:
> (in the <HEAD>)
>
> <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
>
> Though I don't know why it wouldn't work from the servlet. Have you tried
> telnetting to your box and issuing an HTTP request manually? Perhaps the
> headers are not actually getting set. This can happen if you send any
> output to the output stream before setting the headers.
>
> Joe Laffey
> LAFFEY Computer Imaging
> St. Louis, MO
> ----------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
