We were previously catching NoMethodError and interpreting it as
MethodNotSupported. This led to cases where a NoMethodError thrown
deep in a call stack led to the wrong HTTP response code. To fix this,
we tighten up the handling to require a NotImplementedError on the
method call.
We were previously catching
NoMethodErrorand interpreting it asMethodNotSupported. This led to cases where aNoMethodErrorthrown deep in a call stack led to the wrong HTTP response code. To fix this, we tighten up the handling to require aNotImplementedErroron the method call.