ESI headers fix rendered obsolete in sf2.1.10 #2
Description
The parts of the bundle which address this problem:
Allows parts of a view to be cached through ESI, even if the master response has a "private" Cache-Control header (Symfony2 will be default force the entire response to be public). This replicates the sf_cache_key behaviour of Symfony of 1.4 which allowed for easy partial caching.
Are no longer necessary, as they were fixed fixed internally in Symfony on May 1, 2013 in commit 2b554d77. However, the ability to use ESI in JSON is still missing (I believe), so when I get some time I'll look at refactoring that out separately.