From: James Tucker <jftucker@gmail.com>
To: rack-core@googlegroups.com, rack-devel@googlegroups.com,
ruby-talk-google@googlegroups.com
Subject: [ANN] Rack 1.4.1, a modular Ruby webserver interface
Date: Sun, 22 Jan 2012 22:51:59 -0800 [thread overview]
Message-ID: <D917D3C0-73D7-444D-AC06-313EF65BB445@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]
Hello,
Today we are proud to announce the release of Rack 1.4.1.
= 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.
== Changes
* January 22nd, 2012: Twenty fifth public release 1.4.1
* Alter the keyspace limit calculations to reduce issues with nested params
* Add a workaround for multipart parsing where files contian unescaped "%"
* Added Rack::Response::Helpers#method_not_allowed? (code 405)
* Rack::File now returns 404's for illegal directory traversals
* Rack::File now returns 405's for illegal methods (non HEAD/GET)
* Rack::Cascade now catches 405 by default, as well as 404
* Cookies missing '--' no longer cause an exception to be raised
* Various style changes and documentation spelling errors
* Rack::BodyProxy always ensures to execute it's block
* Additional test coverage around cookies and secrets
* Rack::Session::Cookie can now be supplied either secret or old_secret
* Tests are no longer dependent on set order
* Rack::Static no longer defaults to serving index files
* Rack.release was fixed
== Where can I get it?
You can download Rack at
http://chneukirchen.org/releases/rack-1.4.1.tar.gz (upload pending at time of writing)
http://rubyforge.org/projects/rack
Alternatively, you can checkout from the development repository with:
git clone git://github.com/rack/rack.git
cd rack && git checkout rack-1.4 # for this release
Happy hacking and have a nice day,
James Tucker
on behalf of the Rack Core Team.
e822bb1c1dd9306f1f4cc6c7c208ac3fe0aa4018 rack-1.4.1.tar.gz
6a4c6c954d7fa87064b84afad720434402b6d257 rack-1.4.1.gem
[-- Attachment #2: Type: text/html, Size: 5244 bytes --]
reply other threads:[~2012-01-23 6:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D917D3C0-73D7-444D-AC06-313EF65BB445@gmail.com \
--to=rack-devel@googlegroups.com \
--cc=rack-core@googlegroups.com \
--cc=ruby-talk-google@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).