I have mixed feeling about the subject following some tests I’ved made, and took also the weekend to think of it a bit before answering.
A. In order to turn off the response, we need to entangle ourself more with Webrick.
I was unable to access the response settings at all with the current way we implement things.
B. Moving to Puma, means a lot of other work such as supporting
scl, packaging will change, and I haven’t researched how to do it, but following a lot of reading about both Rack and Webrick, I think it’s more or less the same as Webrick in that case.
Being more server agnostic means that we need to inject code on runtime based on the server type.
But it can render new issues that I don’t really think we should have.
That’s why I have mixed feelings here.
I dislike the idea that just because of settings we are failing here, but making SP more entangled with a single server I’m not sure is the proper way to go as well.
BTW I didn’t test a standalone Webrick app that is fully configured, because of the above issue.