-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve user experience when using Puma #79
Comments
This will cause the same issue in the browser with Puma, but at least it will report the error to the console: run ->(env) {
require_relative 'abc'
[200, {}, []]
} |
I'll report it to Puma anyway because it behaves differently when |
Since this is server specific, you should probably report it to the server developers. If you want to rescue exceptions in your Roda application instead of raising them to the server, use the error_handler plugin. |
Hi Jeremy, I'm not sure whether this Puma's behavior is intentional or not. But try running this on Puma:
In Webrick we can see immediately what is the problem but Puma will ignore it silently and would cause ERR_EMPTY_RESPONSE error in Chrome. I guess it would be a good idea for Puma to rescue Exception on
call
and take some action rather than letting it propagate to the web server. What do you think?The text was updated successfully, but these errors were encountered: