Since Twig has been implemented, when the API encounters an exception it parses the error via an error document and the JSON response header is missing. It should log the error in the error log (this part is already happening correctly), return 500 Internal server error as before (and - if running in development mode - output the error details directly w/o parsing them in a template).
Since Twig has been implemented, when the API encounters an exception it parses the error via an error document and the JSON response header is missing. It should log the error in the error log (this part is already happening correctly), return 500 Internal server error as before (and - if running in development mode - output the error details directly w/o parsing them in a template).