I was able to get ESI's to work with the built in Symfony reverse proxy. But
then i switched to Varnish and they weren't behaving the same.
I can make ESI work correctly if I manually put the <esi:include> in the
template. But if i use:
{% render '...:news' with {}, {'standalone': true} %}
Then it just renders the "component" inline and not using an ESI. I do have
esi: { enabled: true }
in my config.yml.
I noticed if i changed the service definition in
FrameworkBundle\Resources\config\esi.xml from:
<service id="esi" class="%esi.class%" public="false" />
to:
<service id="esi" class="%esi.class%" public="true" />
then the ESI's work as expected. I don't understand the DIC stuff well
enough yet to know if this is a bug or if i'm just doing something wrong.
Any ideas? Is anyone using sf2 beta1 with varnish and ESI's ?
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
