On 12 août, 05:14, cd34 <[email protected]> wrote: > In your browser, is it set to verify once or verify every time for > page updates? I checked and when I installed it, it worked as > expected and I used it as a model for a project. If I recall, pylons > isn't writing expire times on that app.
I don't know how to modify the caching of firefox3, but I don't think it is the source of the problem, since the updates give the various versions more or less cyclically. > > If shift-reload fixes the problem, I would suspect your browser is > caching a bit aggressively. Alternatively, I believe you can set the > expire=0 on the render call which may force expire times to be set. I've also tried the option expire_cache=0 in render, but it has no effect on the phenomenon. I rather thought (but I know nothink about this subject) of a pool problem in paste or sqlalchemy. Many thanks for your answer, Etienne -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
