> Frank Maas wrote:
>
>> What you can try is to update the Last-Modified header on each
>> request. Bear in mind that this won't work for requests that are made
>> within the same second. To probably state the obvious: it is
>> necessary that you set the header to the timestamp of the request,
>> not to the timestamp of the underlying image!
>
> I'd prefer to get no_cache(1) working, but will keep the various
> date-forcing ideas as backups.
Well good luck. IMHO no_cache(1) is working fine and is this a client-side
"problem". Webcam viewers have the same problem. There it is solved by
appending a dummy time-related variable to the request, like
<img src="/ImageServer/Image&dummy=1234567">
For some browsers the mere fact that the request was made with parameters
is enough reason to never use it again, for others (that remember the
complete request) you need to change the value for dummy. There are
Javascript bits to do this.
Again good luck!
Frank
