Hi Bill,

I�m returning and I�ll test your suggestion. Due to time problems I did the
hard solution, creating in the application a back function where the link
was build with a CSP token, using the same request parameters.

Thanks for All.

"Bill McCormick" <[EMAIL PROTECTED]> escreveu na mensagem
news:[EMAIL PROTECTED]
> We switched to HTTP 1.1 headers in this time frame and also made the
> change Peter references below. There is an Expires property of the
> %response object you can set to allow the pages to be cached on the
> browser.
>
> Peter Cooper wrote:
> > Carlos
> >
> > I wonder if it's the settings in the HTTP headers that have changed
> > between Cache versions
> >
> > from memory Dev added these headers at some point
> >
> > On Cache 5.0.4 they are
> > EXPIRES: Thu, 29 Oct 1998 17:04:19 GMT
> > PRAGMA: no-cache
> >
> > ie the EXPIRES  is set always before the current date/time
> >
> > have a look at the headers with TCPtrace
> > www.pocketsoap.com
> >
> > try it on the two different versions and see what is being sent by
> > Cache
> >
> > I assume that you are using exactly the same browser to test the
> > different versions
> >
> >
> > Peter
> >



Reply via email to