You are talking about different things.
response.setHeader("Cache-Control", "no-Cache");
tells an http 1.1 client not to cache the page.
Your work directory has nothing to do with that.
AFAIK you have to clean your work directory manualy as tomcat doesn't
remove pages that no longer exist. (This is not a bug, but a feature, it
allows to deploy an application with just the class files and no source
files).
> -----Ursprungliche Nachricht-----
> Von: Joel Rees [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 30. Januar 2002 10:21
> An: Tomcat Users List
> Betreff: cached jsp pages when "no cache" specified still
> there after page is gone
> response.setHeader("Cache-Control", "no-Cache");
>
> specified, yet they have been cached, and remain in the work
> directory after
> the actual pages have been deleted, and the server has been re-booted
> several times.
>
> (These are test pages on a test server.)
>
> Is this normal? Are there some settings I should look for?
>
> Joel
> Alps Giken Kansai Kaihatsubu
> Suita, Osaka, Japan
>
>
>
>
>
> --
> To unsubscribe: <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
