Pierre

> You should be able to route the deprecation channel to wherever you want Those deprecations, i.e. those triggered using `trigger_error('Foo', E_USER_DEPRECATED)` are in the `php` channel, not the deprecation...

OK, I admit, the original issue wasn't really about those, but that I may have hijacked it: the original issue author did point his/her finger on the same piece of...

Don't take those words seriously, I honestly do not want any harm: I am very much appreciating all the hard work and all the time contributors give to this project....

@nicolas-grekas @jkobus I honestly think that the line I was pointing at a few comment above should be removed, I don't see any valid reason for the error handler to...

> 2. E_USER_DEPRECATED are always silenced So you mean by "silenced" that the PHP handler will not be run for those, took me a while to figure that one out....

> Most if not all deprecation are triggered with @trigger_error(). That is: error_level() returns 0. The reporting level you can set before is just overridden during the call. ~~Thank you...

OK I get it now, sorry I misread your comment. Now, how do I silence them back when it's rightful to do so ? I don't see how I can...

And moreover, it unsilence them always, it does not honour error_level() configuration, should it be read at `__construct()` time and set as a property on which to compare ? This...

I have the same error here.

In my case, I have a fixed number of allowed origins, so I was able to workaround this limitation using this procedure: First in `config/services.yaml`: ```yaml parameters: computed_absolute_url: "%router.request_context.scheme%://%router.request_context.host%%env(ABSOLUTE_URL_PORT)%%router.request_context.base_url%" #...