sfCacheFilter seems to use currentInternalUri as cache key.

After a forward, currentInternalUri is the same as the first action uri.

This can explain that Action B caching doesn't work.

Why don't base the cache key on module/action/parameters, in fact  
current action uri ?

Could I create a ticket as a Sf bug ?
--
Nicolas CHARLOT
http://www.isics.fr




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to