> I'm not sure if I can really spend any more of my company's time diagnosing this problem! Certainly the change has worked, and could be useful for anyone in a similar situation.
No worries. This helps! I'm going to look out for something like this as well now, and will probably need to patch with your changes. It is somewhat likely the proxy is involved in the behaviour - not that I'm aware of a specific caching feature in any proxies out there but (after I just finished 5 years of working on routers) it does sound like a likely "feature" candidate. I think this would affect a lot of other (than Django) web applications as well. Should this decorator be added to the generic views? I can see arguments either way. Perhaps it is safer to come up with a different generic view (or a parameter) if you never want to cache? I would also suggest we add a comment to the Forms documentation to recommend using this decorator. Good find! -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers -~----------~----~----~----~------~----~------~--~---
