Catch exceptions in HTTP Browser
Currently any exceptions caused by controllers etc. are not caught by the virtual browser. In order to make the behavior of the Browser class more realistic, these should be converted into a string and a 500 status should be set for the response.
This affects the InternalRequestEngine only.
[TASK] Handle exceptions in virtual HTTP browser
The virtual HTTP browser now catches any exceptions
and returns the exception information in the response
rather than letting the actual exception slip through.