Goliath swallows server errors as 400 about goliath HOT 6 CLOSED

Oh, so the extra 400 response is related to using a browser for an API that wants to give a JSON response. Still doesn't make a lot of sense to me though.

from goliath.

If the browser is chrome, the second request is for favicon.ico usually.

from goliath.

Exceptions are caught and handled by the API. The problem being, if you throw an exception inside the API it will end up in no-where land unless it's caught. The middlewares would have already returned at that point and the ASYNC_CALLBACK has to be used. So, we catch the exception, turn it into a 400 response, and fire the ASYNC_CALLBACKS.

We could possibly also stuff the exception into rack.exception so you can still access it if desired. Then, if you want, you can change the response in your async middleware for exceptions.

Would that work for you?

from goliath.

Yes, I need access to the original exception, so rack.exception would be good. The other issue is the use of a 400 error code, which indicates a client error. In this case it should be a 500.

from goliath.

K, feel free to move it to a 500 from a 400 and add in rack.exception.

from goliath.

pull request in #51

from goliath.