Errors such as 404 and 500 should be handled automatically without the developer having to set anything up. Currently, throwing a new HttpNotFound() from a go() function displays the error uncaught exception message - this should show a blank screen by default (with a 404 error code), or the 404 page, if there's a _404.html in the page directory.
g105b
commented
2 months ago
Errors such as 404 and 500 should be handled automatically without the developer having to set anything up. Currently, throwing a new
HttpNotFound()from ago()function displays the error uncaught exception message - this should show a blank screen by default (with a 404 error code), or the 404 page, if there's a _404.html in the page directory.