@dbu Better keeping that in a separate listener, and ensure that it happens *after* the firewall, for proper context generation (e.g. hash based on roles, and in eZ based on repository permissions and limitations).

@joelwurtz Firewall has priority 8 and occurs after routing (priority 32). So in the end using the request matcher would not have a strong impact. However, this is an overhead we could easily drop as already mentioned.