I'm not sure it's fair to qualify this as a "bug" considering you're logging it against new development that hasn't been committed... but the "solution" is to provide webob with a complete response object.
I'm not sure it's fair to qualify this as a "bug" considering you're logging it against new development that hasn't been committed... but the "solution" is to provide webob with a complete response object.