The simple answer to the topic question is: No. This apparent 404 handling is a side-effect of the routing being done by composer and has not been looked at for actual processing and displaying of any associated messages. It might be as simple as looking at the response header and just displaying a simple/proper message but this is the first time anyone's actually mentioned this so there aren't even language strings for the responses.

in fact, you use the url rewriting to hide the app.php file, isn't it ?
So when you try to access to /other_directory/file_gone.txt the url is rewrited to app.php/other_directory/file_gone.txt and phpBB tries to load a route matching /other_directory/file_gone.txt. But no route matchs so an error 404 is displayed.

[SITENAME] and [SEARCH] obviously linked to correct places. In fact, even phpbb.com itself suggests a 'Search' on error pages.

The language could be added to the 'Topic does not exist' and 'Forum does not exist' error messages too?
I've created custom error pages on my 3.0.12 site so I guess I'm just used to seeing a little more information than the current RC2 setup...

All urls that don't hit a file match app.php which then sends responses. I guess we should add a controller/page for 404 handling, if not an extension could do it. See http://symfony.com/doc/current/componen ... tion-event for how or create a route to match /.? and set it to allow / in the url, send that to a controller, make sure it's the lowest priority, then make that controller throw a 404 template and 404 headers.

You could also look at symfony/TwigBundle internals for twig.exception_controller (Symfony\Bundle\TwigBundle\Controller\ExceptionController if I recall correctly)

Formerly known as Unknown Bliss

psoTFX wrote:
I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"