Exception in script execution results in HTTP status 200 instead of 500

Issue description

When an ordinary exception is thrown in a script. A "script" in this case is a special kind of service, namely a POST service without representational component which echos and has output buffering turned off.

Rejection comment

This is by design. Since all HTTP headers must precede any output, we must send some header (in our case 200) in order to be able to start outputting (= sending a body) to the client. The error that happens afterwards cannot send another HTTP status since we already write the body which comes after the headers. Therefore we just accept that in the case of scripts the exception is not responded with a more appropriate status code.

Reporting date

2026-06-05

Reported by

Robert Cerny

Rejection date