--- Comment #10 from Mark Thomas <> ---
A quick update.

I believe the refactoring to enable the application/container error handling to
handle error reporting is complete. The errors that aren't processed this way
- any error that is so severe it requires the immediate closure of the network
- any error that occurs after the request/response has left the standard
processing pipeline (i.e. once it is too late for the application error
handling or the ErrorReportValve to do anything).

This has only been completed for 9.0.x and - given the refactoring involved -
is unlikely to be back-ported.

Next up is extended in the ErrorReportValve to enable static pages to be used
for given errors.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to