Not support custom 500 Internal Server Error about nowin

[Bobris]

It is little bit of feature - I am expecting when you have 500, application is in so bad state that any response is better to ignore ... So I am not sure if or how to change it right now ... Will think about it.

[Bobris]

It could possibly leak sensitive information (so look at it also from security point of view)

[aaasoft]

I think here should add a config or property to switch user can handle 500 theirself or not.

[comphilip]

Another 5xx status code, while according to RFC 7231, they are for specified error cases. I cannot use 4xx because the error is not caused by client request but invalid state of server (like DB connection problem, disk out of usage and any other unexpected exceptions).

In RFC 7231: Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.

Workaround is use another 5xx not defined in RFC 7231. User agent should treat undefined 5xx status code as 500.

[Bobris]

I think I will force this 500 handling only if you will throw exception from App (and don't catch it). So you will be able to define "catch" middle-ware which can convert it to 500 with custom content.

[serialseb]

I'd think you should lay off from anything but catching exceptions and generating 500. In the other scenarios, middlewares can be added easily enough without nowin supporting it

[comphilip]

"catch" middle-ware is a good solution. Transport2HttpHandler class still needs changes to support this. Its ResponseFinished method is executed after middlewares.

[Bobris]

I will do this after #39. I hope both should be finished over the weekend...