You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I tried out Puma, but it seems to fail on some specific requests. It shows the error in the response body, not stdout/stderr, which I think is an issue that should be fixed in itself, because it reveals details about the environment to potential attackers, just like the PHP exceptions do. I use Puma via its Rack::Handler interface, which I guess isn't a common thing to do anymore, but a practical neccessity due to the way my app works (it's daemon first, http handling is just one of the interfaces amongst potentially others).
Anyhow, the test that causes the exception is part of my self-test framework. It fails every time on Puma combined with ruby-1.9.3: ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.3.0]
It works just fine on Puma on Rubinius, which is: rubinius 2.0.0dev (1.8.7 caa57c20 yyyy-mm-dd JI) [x86_64-apple-darwin11.3.0]
Other rack handlers, like Mongrel, Thin and WEBrick, amongst others, pass the tests just fine, so this is really either Puma-specific or something else that was triggered specifically with Puma.
Hi, I tried out Puma, but it seems to fail on some specific requests. It shows the error in the response body, not stdout/stderr, which I think is an issue that should be fixed in itself, because it reveals details about the environment to potential attackers, just like the PHP exceptions do. I use Puma via its Rack::Handler interface, which I guess isn't a common thing to do anymore, but a practical neccessity due to the way my app works (it's daemon first, http handling is just one of the interfaces amongst potentially others).
Anyhow, the test that causes the exception is part of my self-test framework. It fails every time on Puma combined with ruby-1.9.3:
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.3.0]It works just fine on Puma on Rubinius, which is:
rubinius 2.0.0dev (1.8.7 caa57c20 yyyy-mm-dd JI) [x86_64-apple-darwin11.3.0]Other rack handlers, like Mongrel, Thin and WEBrick, amongst others, pass the tests just fine, so this is really either Puma-specific or something else that was triggered specifically with Puma.
Response:
Request (not 100% accurate data, as it's copypasted from the browser's network console):
The text was updated successfully, but these errors were encountered: