New in Symfony 2.4: Easier debugging of not-found resources

October 28, 2013 · Published by Avatar of Fabien Potencier Fabien Potencier

Warning: This post is about an unsupported Symfony version. Some of this information may be out of date. Read the most recent Symfony Docs.

scourgen hung

Contributed by
scourgen hung
in #8708.

When a 404 occurs in a web application, knowing the root cause helps fixing the problem: is it someone trying to hack your website by trying different well-known URLs? Is it a dead-link on your website? or on another one? If the 404 comes from your website, fixing it should be relatively easy.

The only source of information about the cause is the HTTP Referer header. And even if it cannot be trusted, it can help nonetheless. That's why as of Symfony 2.4, the HTTP Referer is added in the NotFoundHttpException exception message thrown by the router listener.

Published in #Living on the edge

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

Comments

Avatar of Dirk Luijk
Dirk Luijk said on Oct 28, 2013
Great, thanks!
Avatar of Antonio Mansilla
Antonio Mansilla said on Oct 29, 2013
Nice and needed feature. Thanks again!! ;)
Avatar of Maximilian Reichel
Maximilian Reichel Certified said on Oct 29, 2013
+1
Avatar of Loïc Vernet
Loïc Vernet Certified said on Oct 30, 2013
Good idea.
Avatar of Dawood RASHID
Dawood RASHID said on Oct 31, 2013
Surely, it would help

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.