> > >
> >
> > If it's for CForms, we can add the setting of no-cache headers in
> > Form.js since it's very unlikely that a form pipeline will be
> > cacheable.
>
> Think we tried similar things (in flowscript), but we found
> the problem Bertrand also faced about the fact, that you have
> to set the headers on the pipeline the serializer is used
> from (but all requests for example arrive at a catch all
> matcher, which does not know wether it includes a form or not).
>
> Do you think you can set it globally for the request in
> Form.js? I tried directly manipulating the
> HttpServletResponse, but obviously, this resulted in correct
> behavior on the first request, but consecutive cached
> responses did not have this direct HttpServletResponse
> manipulation, so this implied uncacheable pipelines in
> cocoon, which of course, I did not want either.
Hmmm, reading this again, of course, CForms aren't cached anyway of course....
>
> But, I am curious about a possible solution
>
> Ard
>
> >
> > Also, for other flowscripts there could be a parameter on the
> > <map:flow>
> > instruction stating the flowscript engine has to always set
> > the no-cache
> > headers.
> >
> > Sylvain
> >
> > --
> > Sylvain Wallez - http://bluxte.net
> >
> >
>
|