Rack::Parser is a Rack Middleware for parsing post body data for JSON, XML, and custom content types using MultiJson, MultiXML, or any thing that you want to use.

What this allows your rack application to do is decode/parse incoming post data into param hashes for your applications to use.

Installation

install it via rubygems:

or put it in your Gemfile:

# Gemfile

gem 'rack-parser', :require => 'rack/parser'

Usage

In a Sinatra or Padrino application, it would probably be something like:

# app.rb

use Rack::Parser

Content Type Parsing

By default, Rack::Parser uses MultiJson and MultiXml to decode/parse your JSON/XML Data. these can be overwritten if you choose not to use them. However, through using them you can just as easily leverage the engine of your choice by setting the engine like so:

# app.rb

MultiJson.engine = :yajl  # Yajl-ruby for json decoding
MultiXml.parser  = :libxml # libxml for XML parsing

use Rack::Parser

To set your own custom engine that perhaps neither MultiJson or MultiXml support, just make it a Proc:

use Rack::Parser, :content_types => {
  'application/json' => Proc.new { |body| MyCustomJsonEngine.do_it body },
  'application/xml'  => Proc.new { |body| MyCustomXmlEngine.decode body },
  'application/roll' => Proc.new { |body| 'never gonna give you up'     }
}

Error Handling

Rack::Parser comes with a default error handling response that is sent if an error is to occur. If a logger is present, it will try to warn with the content type and error message.

You can additionally customize the error handling response as well to whatever it is you like:

use Rack::Parser, :error_responses => {
  'default'          => Proc.new { |e, content_type| [500, {}, ["boo hoo"] ] },
  'application/json' => Proc.new { |e, content_type| [400, {'Content-Type'=>content_type}, ["broke"]] }
  }

The error handler expects to pass both the error and content_type so that you can use them within your responses. In addition, you can override the default response as well.

If no content_type error handling response is present, it will use the default.

Inspirations

This project came to being because of:

• Niko Dittmann's rack-post-body-to-params which some of its ideas are instilled in this middleware.
• Rack::PostBodyContentTypeParser from rack-contrib which proved to be an inspiration for both libraries.

External Sources/Documentations

• Sinatra recipes - mini tutorial on using rack-parser (thanks to Eric Gjertsen)

Contributors

• Stephen Becker IV - For initial custom error response handling work.
• Tom May - skip loading post body unless content type is set.

Copyright

Copyright © 2011 Arthur Chiu. See MIT-LICENSE for details.