Comments (2)
I thought Zend Expressive has default exception and other response handling built in i.e. 404, methodNotAllowed etc, instead of just bombing out on all problems... or is it up to the developer to write this core functionality?
Expressive has error handling included, even v1 (which is not supported anymore I think). It has default 404 and error handlers and comes with WhoopsErrorHandler for debugging purposes.
I've wasted so much time searching for examples, but as usual nothing that that works... I cannot believe this is so badly documented (or an architecture flaw in v1?)
I wonder how much time you have spend or where you searched because it is documented here: https://docs.zendframework.com/zend-expressive/v1/features/error-handling/
If you used the skeleton to install expressive it is added by default.
I mostly use PHP Slim and it has the above baked in, the developer can also override it with custom handlers...simple and to-the-point.
Expressive works the same, you can override the default middleware with custom ones.
However, when I switch php error reporting on I can see an exception raised by Diactoros (...Unsupported response reason phrase; must be a string, received NULL...zendframework/zend-diactoros/src/Response.php:185 Stack trace...) , but no trace/indication of where the problem actually occurred, when php error reporting is off then I get a blank screen with server 500 error.
This sounds like a bug we discovered a while ago in Diactoros which was fixed in verions 2.0.3 and 2.1.1. But since you are using expressive v1, I'm not sure if it affects you.
The case was that before the middleware pipeline in expressive was started, an exception was thrown. Since the error handling didn't start yet, it couldn't catch the exception obviously, hence the 500 blank pages.
With the little information you gave I can't tell if this affect you, but I hope this helps you somehow figuring out what is wrong.
Originally posted by @geerteltink at zendframework/zend-expressive#653 (comment)
from mezzio.
Thank you for the reply.
What I have found to work in v1 is the following:
At the top of my bootstrap (/public/index.php) I have this:
error_reporting(E_ALL);
ini_set('display_errors', 1);
ini_set("display_startup_errors", 1);
Then in my config/autoload/local.php
'zend-expressive' => [
'raise_throwables' => true,
]
Without raise_throwables the problem remains, even with PHP error reporting on, so this is vital.
I'm working on an old legacy system, but I'm sure if I had to implement try...catch along with the above I could switch off display_errors in production and catch/log these errors.
Originally posted by @TradeSharer at zendframework/zend-expressive#653 (comment)
from mezzio.
Related Issues (20)
- Create `Mezzio\ApplicationPipeline` implementation for better static code analysis HOT 1
- Missing good examples of configuration template paths for laminas-view in mezzio HOT 3
- Replace `RequestHandlerRunner` factory with `RequestHandlerRunnerInterface` factory HOT 3
- Page with the description of the installation is missing
- Dependency Dashboard
- [RFC]: Provide an ApplicationProgrammaticConfigDelegator that pairs with ApplicationConfigInjectionDelegator HOT 4
- Script MezzioInstaller\OptionalPackages::install handling the pre-install-cmd event terminated with an exception HOT 3
- Upgrading to PHP 8.2 breaks Dependency Injection HOT 9
- [RFC]: Remove Pimple from Mezzio documentation and from Mezzio skeleton HOT 3
- bin/mezzio-tooling is incompatible with mezzio/mezzio-tooling v2 HOT 7
- [RFC]: Deprecate `ApplicationConfigInjectionDelegator` and `Application#post`, etc.
- Provide `RouteCollectorInterface` and `MiddlewarePipeInterface` delegators to supersede `ApplicationConfigInjectionDelegator` HOT 1
- jsoumelidis/zend-sf-di-config[0.4.0, ..., 0.4.1] require php ^7.1 -> your php version 8.0.99 HOT 1
- PhpDebugBar documentation is outdated. HOT 1
- [RFC]: Remove Aura.Di from Mezzio documentation and from Mezzio skeleton HOT 1
- [RFC]: Add Symfony DependencyInjection as container HOT 2
- [RFC]: Add chubbyphp-container as container
- Move router integration tests to router packages
- PHP 8.1 Support HOT 12
- Support for laminas-httphandlerrunner 2.x versions HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mezzio.