OK, that makes sense then. I'll give that a whirl, thanks for the advice.
Ben Pope
Geert Josten wrote:
>
> Hi there,
>
> Wrap (part of) the matches in a pipeline with
> type="noncaching". As far as I know, request-params
> are ignored in identifying cached results. :-(
>
> Cheers,
> Geert
Hi there,
Wrap (part of) the matches in a pipeline with type="noncaching". As far as I know, request-params
are ignored in identifying cached results. :-(
Cheers,
Geert
Ben Pope wrote:
Anybody?
I should note that not putting an .html or .xml on the end works nicely, so
it seems that the wrapper
Anybody?
I should note that not putting an .html or .xml on the end works nicely, so
it seems that the wrappers are to blame.
Ben Pope wrote:
>
> Hi,
>
> I have some generic pipelines that return data in xml.
>
> I then wrap those pipelines with generator / serialisers to
> choose the outp
Hi,
I have some generic pipelines that return data in xml.
I then wrap those pipelines with generator / serialisers to choose the
output type. E.g.,
...
It looks as if the output gets cached, when I request a form like:
http://localhos
