From fed426546eca5b9bd9d496ffcc703f1c5d4ffd5f Mon Sep 17 00:00:00 2001 From: shoully Date: Sat, 20 Dec 2014 06:36:19 -0800 Subject: [PATCH] Updated 10 Error Handling (markdown) --- 10 Error Handling.md => 09 Error Handling.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename 10 Error Handling.md => 09 Error Handling.md (93%) diff --git a/10 Error Handling.md b/09 Error Handling.md similarity index 93% rename from 10 Error Handling.md rename to 09 Error Handling.md index adc1c95..b98ce46 100644 --- a/10 Error Handling.md +++ b/09 Error Handling.md @@ -1,4 +1,4 @@ -## Errors and Exceptions +### Errors and Exceptions All errors and exceptions are caught by Flight and passed to the `error` method. The default behavior is to send a generic HTTP `500 Internal Server Error` response with some error information. @@ -12,7 +12,7 @@ By default errors are not logged to the web server. You can enable this by chang Flight::set('flight.log_errors', true); -## Not Found +### Not Found When a URL can't be found, Flight calls the `notFound` method. The default behavior is to send an HTTP `404 Not Found` response with a simple message. You can override this behavior for your own needs: