如何在rails 5中拯救ActionDispatch :: ParamsParser :: ParseError并返回自定义API错误?

nak*_*kwa 8 api ruby-on-rails rack-middleware rails-api ruby-on-rails-5

每当针对我的仅使用API​​的Rails 5.x应用程序发送格式错误的JSON时,我都会收到异常,并且Rails将整个堆栈跟踪作为JSON返回.显然,我想回答一个很好的,自定义的,格式化的错误.

=> Booting Puma
=> Rails 5.0.0.1 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
Puma starting in single mode...
* Version 3.6.0 (ruby 2.3.0-p0), codename: Sleepy Sunday Serenity
* Min threads: 5, max threads: 5
* Environment: development
* Listening on tcp://localhost:3000
Use Ctrl-C to stop
Started POST "/api/v1/identities/" for ::1 at 2016-10-26 18:42:32 +0200
  ActiveRecord::SchemaMigration Load (0.3ms)  SELECT "schema_migrations".* FROM "schema_migrations"
Error occurred while parsing request parameters.
Contents:

{
    "whatever": "ewewgewewtwe"
    "malformed_json": ";
}

ActionDispatch::ParamsParser::ParseError (822: unexpected token at '{
    "whatever": "ewewgewewtwe"
    "malformed_json": ";
}'):

actionpack (5.0.0.1) lib/action_dispatch/http/parameters.rb:71:in `rescue in parse_formatted_parameters'
actionpack (5.0.0.1) lib/action_dispatch/http/parameters.rb:65:in `parse_formatted_parameters'
actionpack (5.0.0.1) lib/action_dispatch/http/request.rb:366:in `block in POST'
rack (2.0.1) lib/rack/request.rb:57:in `fetch'
rack (2.0.1) lib/rack/request.rb:57:in `fetch_header'
actionpack (5.0.0.1) lib/action_dispatch/http/request.rb:365:in `POST'
actionpack (5.0.0.1) lib/action_controller/metal/params_wrapper.rb:282:in `_wrapper_enabled?'
actionpack (5.0.0.1) lib/action_controller/metal/params_wrapper.rb:231:in `process_action'
activerecord (5.0.0.1) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
actionpack (5.0.0.1) lib/abstract_controller/base.rb:126:in `process'
actionpack (5.0.0.1) lib/action_controller/metal.rb:190:in `dispatch'
actionpack (5.0.0.1) lib/action_controller/metal.rb:262:in `dispatch'
actionpack (5.0.0.1) lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
actionpack (5.0.0.1) lib/action_dispatch/routing/route_set.rb:32:in `serve'
actionpack (5.0.0.1) lib/action_dispatch/journey/router.rb:39:in `block in serve'
actionpack (5.0.0.1) lib/action_dispatch/journey/router.rb:26:in `each'
actionpack (5.0.0.1) lib/action_dispatch/journey/router.rb:26:in `serve'
actionpack (5.0.0.1) lib/action_dispatch/routing/route_set.rb:725:in `call'
rack (2.0.1) lib/rack/etag.rb:25:in `call'
rack (2.0.1) lib/rack/conditional_get.rb:38:in `call'
rack (2.0.1) lib/rack/head.rb:12:in `call'
activerecord (5.0.0.1) lib/active_record/migration.rb:552:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
activesupport (5.0.0.1) lib/active_support/callbacks.rb:97:in `__run_callbacks__'
activesupport (5.0.0.1) lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
activesupport (5.0.0.1) lib/active_support/callbacks.rb:90:in `run_callbacks'
actionpack (5.0.0.1) lib/action_dispatch/middleware/callbacks.rb:36:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/executor.rb:12:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties (5.0.0.1) lib/rails/rack/logger.rb:36:in `call_app'
railties (5.0.0.1) lib/rails/rack/logger.rb:24:in `block in call'
activesupport (5.0.0.1) lib/active_support/tagged_logging.rb:70:in `block in tagged'
activesupport (5.0.0.1) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (5.0.0.1) lib/active_support/tagged_logging.rb:70:in `tagged'
railties (5.0.0.1) lib/rails/rack/logger.rb:24:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/request_id.rb:24:in `call'
rack (2.0.1) lib/rack/runtime.rb:22:in `call'
activesupport (5.0.0.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/executor.rb:12:in `call'
actionpack (5.0.0.1) lib/action_dispatch/middleware/static.rb:136:in `call'
rack (2.0.1) lib/rack/sendfile.rb:111:in `call'
railties (5.0.0.1) lib/rails/engine.rb:522:in `call'
puma (3.6.0) lib/puma/configuration.rb:225:in `call'
puma (3.6.0) lib/puma/server.rb:578:in `handle_request'
puma (3.6.0) lib/puma/server.rb:415:in `process_client'
puma (3.6.0) lib/puma/server.rb:275:in `block in run'
puma (3.6.0) lib/puma/thread_pool.rb:116:in `block in spawn_thread'
Run Code Online (Sandbox Code Playgroud)

以前我认为可以添加中间件并处理异常如下:

# in config/application.rb

config.middleware.insert_before(ActionDispatch::ParamsError,'BadRequestError')

# middleware

class BadRequestError
    def initialize(app)
        @app = app
    end

    def call(env)
        begin
            @app.call(env)
        rescue ActionDispatch::ParamsParser::ParseError
            Api::ApiController.action(:raise_bad_request).call(env)
        end
    end
end
Run Code Online (Sandbox Code Playgroud)

但是,似乎中间件ActionDispatch::ParamsError已从Rails 5中删除;

我也尝试过其他中间件(例如ActionDispatch :: ShowExceptions),拯救不同的错误,但我的raise_bad_request动作在某种程度上从未被调用过.

我错过了什么,做错了什么,或者是否有其他方法可以使用Rails 5?

谢谢!

Spa*_*Spa 15

更新了使用Rails 5.1和更新版本的答案.(感谢@Edwin Meyer) config.middlware.use现在需要一个类,而不是字符串.

我现在还提到,我把中间件放在了app/middleware.所以没必要.


我有同样的问题,在我的案例中解决起来非常简单.

只需用于application.rb:

config.middleware.use CatchJsonParseErrors

# Instead of
# config.middleware.insert_before ActionDispatch::ParamsParser, "CatchJsonParseErrors"
# I used in my Rails 4 app
Run Code Online (Sandbox Code Playgroud)

我的中间件看起来像这样(来自使用机架中间件捕获无效的JSON解析错误):

# app/middleware/catch_json_parse_errors.rb

class CatchJsonParseErrors
  def initialize(app)
    @app = app
  end

  def call(env)
    begin
      @app.call(env)
    rescue ActionDispatch::ParamsParser::ParseError => error
      if env['HTTP_ACCEPT'] =~ /application\/json/
        error_output = "There was a problem in the JSON you submitted: #{error}"
        return [
          400, { "Content-Type" => "application/json" },
          [ { status: 400, error: error_output }.to_json ]
        ]
      else
        raise error
      end
    end
  end
end
Run Code Online (Sandbox Code Playgroud)

然后当我发送一个无效的json时,响应看起来像这样:

{"status":400,"error":"There was a problem in the JSON you submitted: 743: unexpected token at '{ \"foo\": \"bar\" '"}
Run Code Online (Sandbox Code Playgroud)

您需要提供正确的ACCEPT标题.

希望它也能帮到你.

  • 对于Rails 5.2,要解决的错误现在是`ActionDispatch :: Http :: Parameters :: ParseError` (2认同)

小智 5

我正在运行Rails 5.1.4,我发现需要进行以下修改才能让Spa的解决方案适合我:

在application.rb中 -

1)config.middleware.use的参数似乎是一个类,而不是一个字符串:config.middleware.use CatchJsonParseErrors
2)必须要求catch_json_parse_errors.rb:
require './app/middleware/catch_json_parse_errors'

在catch_json_parse_errors.rb中 -
将行更改
if env['HTTP_ACCEPT'] =~ /application\/json/

if env['HTTP_ACCEPT'] =~ /application\/json/ || env['CONTENT_TYPE'] =~ /application\/json/
如此错误的内容HTTP请求,其中还指定了CONTENT_TYPE但未指定HTTP_ACCEPT.