ZF-10509: Using the functionality of priority to give meaning to the log in the default error controller

Issue Type: Improvement Created: 2010-09-30T12:44:52.000+0000 Last Updated: 2010-12-30T09:42:35.000+0000 Status: Closed Fix version(s): - 1.11.3 (01/Feb/11)

Reporter: Benoît Durand (intiilapa) Assignee: Benoît Durand (intiilapa) Tags: - Zend_Tool

Related issues: Attachments:


Currently, the priority level used for logging is critical in all cases. It makes no sense, because there are differences between a error code 404 and 500 : * a code 500 represents a runtime exception * any resource that does not exist is redirected to the front controller. The traffic by robots or the search for files as the favicon for some browsers lead to an exception no controller. This could be an important source of spam * a typo or dead link can be the source of an exception no action * a configuration error on routes or only use static routes (or too specialized) should throw an exception no route

A code 500 should stay in critical priority, and we should lower the level at warning or notice for the code 404. This can be refined for code 404. An exception due to the absence of a route might need to be raised even in production.


Posted by Benoît Durand (intiilapa) on 2010-12-17T12:13:28.000+0000


Posted by Matthew Weier O'Phinney (matthew) on 2010-12-30T09:42:27.000+0000

Re-opening in order to re-assign fix version.

Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.