On Sep 22, 11:58 pm, Bernhard Schussek <[EMAIL PROTECTED]> wrote: > A third option would be to check whether the uri has been modified > during action execution and if yes, throw a ConfigurationException > informing the user to turn off the cache when modifying the request > parameters (as the page won't be cached anyway, if he does so). >
Not precisely. Caching is turned off only when there are any $_POST or $_GET parameters i.e. http://example.com/foo/bar/baz/13/xyzzy/16 is perfectly cacheable, while http://example.com/fooo/bar?baz=13&baz=16 isn't. It should be possible to rewrite any parameter like baz in the first URL with caching on (like when sanitizing input parameters in my case), so of course this is a bug, which I've filed a while ago. See http://trac.symfony-project.com/trac/ticket/2102 > What do you think about this? I think Symfony needs more man-power :( Fabien alone can't cope with the avalanche of bug reports. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
