Today we are proud to release Rack 1.0, which was close to almost be
= Rack, a modular Ruby webserver interface
Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
The exact details of this are described in the Rack specification,
which all Rack applications should conform to.
== Specification changes in this release
With Rack 1.0, the Rack specification (found in SPEC) changed in the
following backward-incompatible ways. This was done to properly
support Ruby 1.9 and to deprecate some problematic techniques:
* Rack::VERSION has been pushed to [1,0].
* Header values must be Strings now, split on "\n".
* rack.input must be rewindable and support reading into a buffer,
wrap with Rack::RewindableInput if it isn't.
* Content-Length can be missing, in this case chunked transfer
encoding is used.
* Bodies can now additionally respond to #to_path with a filename to
* String bodies are deprecated and will not work with Ruby 1.9, use an
Array with a single String instead.
* rack.session is now specified.
Use Rack::Lint to find out in which ways this possibly broke your
applications and middleware.
* April 25th, 2009: Seventh public release 1.0.0.
* SPEC changes, see above.
* New middleware Rack::Lock.
* New middleware Rack::ContentType.
* Rack::Reloader has been rewritten.
* Major update to Rack::Auth::OpenID.
* Support for nested parameter parsing in Rack::Response.
* Support for redirects in Rack::Response.
* HttpOnly cookie support in Rack::Response.
* The Rakefile has been rewritten.
* Many bugfixes and small improvements.
== Where can I get it?
You can download Rack 1.0 at
Alternatively, you can checkout from the development repository with:
git clone git://github.com/rack/rack.git
cd rack && git checkout rack-1.0 # for this release
== Supported web servers
The included *handlers* connect all kinds of web servers to Rack:
These web servers include Rack handlers in their distributions:
* Phusion Passenger (which is mod_rack for Apache and for nginx)
Any valid Rack app will run the same on all these handlers, without
== Supported web frameworks
The included *adapters* connect Rack with existing Ruby web frameworks:
These frameworks include Rack adapters in their distributions:
* Ruby on Rails
Current links to these projects can be found at
The plethora of useful middleware created the need for a project that
collects fresh Rack middleware. rack-contrib includes a variety of
add-on components for Rack and it is easy to contribute new modules.
== Installing with RubyGems
A Gem of Rack is available. You can install it with:
gem install rack
I also provide a local mirror of the gems (and development snapshots)
at my site:
gem install rack --source http://chneukirchen.org/releases/gems/
Please mail bugs, suggestions and patches to
Mailing list archives are available at
There is a bug tracker at <http://rack.lighthouseapp.com/>.
You are also welcome to join the #rack channel on irc.freenode.net.
The Rack Core Team, consisting of
* Christian Neukirchen (chneukirchen)
* James Tucker (raggi)
* Josh Peek (josh)
* Michael Fellinger (manveru)
* Ryan Tomayko (rtomayko)
* Scytrin dai Kinthra (scytrin)
would like to thank:
* Adrian Madrid, for the LiteSpeed handler.
* Christoffer Sawicki, for the first Rails adapter and Rack::Deflater.
* Tim Fletcher, for the HTTP authentication code.
* Luc Heinrich for the Cookie sessions, the static file handler and bugfixes.
* Armin Ronacher, for the logo and racktools.
* Aredridel, Ben Alpert, Dan Kubb, Daniel Roethlisberger, Matt Todd,
Tom Robinson, Phil Hagelberg, and S. Brent Faulkner for bug fixing
and other improvements.
* Brian Candler, for Rack::ContentType.
* Graham Batty, for improved handler loading.
* Stephen Bannasch, for bug reports and documentation.
* Gary Wright, for proposing a better Rack::Response interface.
* Jonathan Buch, for improvements regarding Rack::Response.
* Armin Röhrl, for tracking down bugs in the Cookie generator.
* Alexander Kellett for testing the Gem and reviewing the announcement.
* Marcus Rückert, for help with configuring and debugging lighttpd.
* The WSGI team for the well-done and documented work they've done and
Rack builds up on.
* All bug reporters and patch contributers not mentioned above.
Copyright (C) 2007, 2008, 2009 Christian Neukirchen <http://purl.org/net/chneukirchen>
Rack is freely distributable under the terms of an MIT-style license.
Rack's Rubyforge project:: <http://rubyforge.org/projects/rack>
Official Rack repositories:: <http://github.com/rack>
rack-devel mailing list:: <http://groups.google.com/group/rack-devel>
Happy hacking and have a nice day,
on behalf of the Rack Core Team.
> Could you update the rdoc on the website? It specification link on the
> front page doesn't link to the latest version of the spec.
The SPEC is now at http://rack.rubyforge.org/doc/SPEC.html
Mail complaints to the RDoc maintainers, which didn't care for
preserving URLs with the last update.
> This is not the latest spec. For example the latest spec should
> mention that rack.input#read must behave like IO#read, but I don't see
> that in the HTML.