In onError Propagate, if the error originates from an HTTP Listener, what status is returned?

In onError Propagate, if the error originates from an HTTP Listener, what status is returned?

• A. 200 OK
• B. 404 Not Found
• C. 500 Internal Server Error
• D. 403 Forbidden

Answer: (C)

When an error occurs in the HTTP Listener path and there isn’t a specific mapping to a different HTTP status, the response indicates a server-side failure. Using onError Propagate in this scenario surfaces the error to the HTTP response, and the default behavior is to return 500 Internal Server Error. This signals that something went wrong on the server during request processing, not a problem with the client. Briefly, a 200 would mean success, 404 would mean the requested resource wasn’t found, and 403 would mean access is forbidden. Those require explicit handling or mapping, but for an unhandled error originating from the HTTP Listener, 500 is the standard response.

When an error occurs in the HTTP Listener path and there isn’t a specific mapping to a different HTTP status, the response indicates a server-side failure. Using onError Propagate in this scenario surfaces the error to the HTTP response, and the default behavior is to return 500 Internal Server Error. This signals that something went wrong on the server during request processing, not a problem with the client.

Briefly, a 200 would mean success, 404 would mean the requested resource wasn’t found, and 403 would mean access is forbidden. Those require explicit handling or mapping, but for an unhandled error originating from the HTTP Listener, 500 is the standard response.