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 webspace manager, which is configured in the core bundle, relies on the request context container parameters router.request_context.host and router.request_context.scheme (see here) as fallback when no actual request object is available. This might happen during cache warming in a functional test.
But if the request context is configured by Symfony's framework.router.default_uri setting like it is described in their docs, the mentioned container parameters still uses the defaults (localhost and http). There is a issue which points this out symfony/symfony#53919.
In my case this leads to wrong url generation in a functional test (kernel test case) when the cache is warmed.
Expected Behavior
Sulu should use the request context values as fallback even if they are configured by the default_uri setting.
Possible Solutions
This can be fixed by using the request context service instead of the container params.
The text was updated successfully, but these errors were encountered:
stollr
added
the
Bug
Error or unexpected behavior of already existing functionality
label
Feb 13, 2024
Actual Behavior
The webspace manager, which is configured in the core bundle, relies on the request context container parameters
router.request_context.host
androuter.request_context.scheme
(see here) as fallback when no actual request object is available. This might happen during cache warming in a functional test.But if the request context is configured by Symfony's
framework.router.default_uri
setting like it is described in their docs, the mentioned container parameters still uses the defaults (localhost and http). There is a issue which points this out symfony/symfony#53919.In my case this leads to wrong url generation in a functional test (kernel test case) when the cache is warmed.
Expected Behavior
Sulu should use the request context values as fallback even if they are configured by the
default_uri
setting.Possible Solutions
This can be fixed by using the request context service instead of the container params.
The text was updated successfully, but these errors were encountered: