Richard van Laak
Richard van Laak
@zip-fa since I've properly configured the Supervisor application to register to Redis on a unique DSN this issue seems resolved for me. After translating [this Russian blogpost](https://medium.com/@alshenetsky/symfony-messenger-redis-%D0%BF%D0%BE%D0%B4%D0%B2%D0%BE%D0%B4%D0%BD%D1%8B%D0%B9-%D0%BA%D0%B0%D0%BC%D0%B5%D0%BD%D1%8C-43f1dbcb8d86) by ะะปะตะบัะตะน ะะปััะตะฝะตัะบะธะน...
I also remember this being quite confusing when I started working with Symfony back then, especially as the variable itself most often is named `$request` already.
Would it be possible to enhance Symfony's Http Cache so it could work together with the `allow_origin` policy, so we do not need to set `forced_allow_origin_value` ?
@fabpot what do you think of this PR? Would be great to have the `@ContentSafe` annotation at our disposal.
> I think we have no other choice than extending the class+service via inheritance here. This could probably be revisited on 3.x, in conjunction with making the ErrorListener more cleanly...
Ah @chalasr fair point, I did not see that it uses extension. My comment solely focussed on the service registration and related event listener priorities. Is there a reason why...
Looking to https://github.com/api-platform/core/commits/main/src/Symfony/EventListener, it seems that there isn't any commit on main that reverts this change?
For reference, feature seems (re)introduced for branch 3.0 via PR https://github.com/api-platform/core/pull/4981
I've also tried the `exceptionToStatus` on the level of the resource, but it also returns a 500 where the mapped 404 is expected: ``` #[ApiResource( provider: ProductProvider::class, exceptionToStatus: [ [NotFoundException::class...
see https://github.com/quicktype/quicktype/pull/1616 for progress