You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The framework has support for rendering "esi" tags. The internal implementation allows to pass objects as parameters of render standalone tags. This is a problem, because if you switch to a real reverse proxy, the objects in the parameters will be nullified.
I think this behavior should be changed to allow users to switch more transparently between a real reverse proxy and the symfony2 implementation.
The framework has support for rendering "esi" tags. The internal implementation allows to pass objects as parameters of render standalone tags. This is a problem, because if you switch to a real reverse proxy, the objects in the parameters will be nullified.
I think this behavior should be changed to allow users to switch more transparently between a real reverse proxy and the symfony2 implementation.
The problem probably lies in the generation of the _internal uri. The code uses the
http_build_query()
method that will not include objects with no public fields: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/HttpKernel.php#L188. Parameters should only be scalars?The text was updated successfully, but these errors were encountered: