[opencms-dev] preview problem

[Alexander Kandzior]

Martin,

sorry but I do not have this 4.6.1 modified jar at hand. It should be
easy enough to re-build it from the 4.6.1 source distribution with ant.

Best Regards,
Alex.

Alexander Kandzior
OpenCms Group / Alkacon Software

> -----Original Message-----
> From: owner-opencms-dev at www.opencms.org 
> [mailto:owner-opencms-dev at www.opencms.org] On Behalf Of Martin Leja
> Sent: Monday, November 04, 2002 1:58 PM
> To: opencms-dev at www.opencms.org
> Subject: Re: [opencms-dev] preview problem
> 
> 
> hi alexander,
> 
> thanks for your answer. Before i start the recompilation of 
> the source i like to know if you happen to have a modified 
> version of the file "<some servlet runtime engine like
> tomcat>\webapps\opencms\WEB-INF\oclib\opencms.jar" at hand containing 
> tomcat>the
> quick fix for opencms 4.6.1.
> 
> I think it should be enough to replace this JAR file with a 
> subsequent restart of the servlet engine in order to fix the 
> IE-offline-preview issue.
> 
> 
> ----- Original Message -----
> From: "Alexander Kandzior" <alex at opencms.org>
> To: <opencms-dev at www.opencms.org>
> Sent: Monday, November 04, 2002 12:55 PM
> Subject: RE: [opencms-dev] preview problem
> 
> 
> > Martin,
> >
> > the problem is related to the OpenCms cache settings. In 
> the offline 
> > project these are set to
> >
> > //HTTP 1.1
> >       resp.setHeader("Cache-Control", "no-cache");
> >       //HTTP 1.0
> >       resp.setHeader("Pragma", "no-cache");
> >
> > in the Classes
> >
> > com.opencms.template.CmsRootTemplate
> > com.opencms.template.cache.CmsUri
> >
> > which causes trouble with later versions of IE because IE 
> seems to be 
> > unable to write the plugin files to its temp directory with this 
> > settings.
> >
> > Quick Fix is to replace above lines with:
> >
> > //HTTP 1.1
> >       resp.setHeader("Cache-Control", "max-age=5");
> >       //HTTP 1.0
> >       // resp.setHeader("Pragma", "no-cache");
> >
> > and recompile the OpenCms core. This will probably be 
> incooperated in 
> > the next release.
> >
> > BTW if anyone is a http header guru I surely would appreciate some 
> > input on a set of better header settings for this caching stuff.
> 
> [...]
> 
>