[ANN] unicorn 0.93.2 - more compatible with Rails

E

Eric Wong

Unicorn is a HTTP server for Rack applications designed to take
advantage of features in Unix/Unix-like kernels and only serve fast
clients on low-latency, high-bandwidth connections. Slow clients should
only be served by placing a reverse proxy capable of fully-buffering
both the the request and response in between Unicorn and slow clients.

* http://unicorn.bogomips.org/
* (e-mail address removed)
* git://git.bogomips.org/unicorn.git

Thanks to Chris Wanstrath for reporting issues with large
POST bodies and for helping me test.

Changes:

Avoid truncated POST bodies with URL-encoded forms in Rails
by switching TeeInput to use read-in-full semantics (only) when
a Content-Length: header exists. Chunked request bodies
continue to exhibit readpartial semantics to support
simultaneous bidirectional chunking.

The lack of return value checking in Rails to protect against a
short ios.read(length) is entirely reasonable even if not
pedantically correct. Most ios.read(length) implementations
return the full amount requested except right before EOF.

A ticket has been opened here to track the issue:
https://rails.lighthouseapp.com/projects/8994/tickets/3343

Also there are some minor documentation improvements.

Eric Wong (8):
Fix NEWS generation on single-paragraph tag messages
Include GPLv2 in docs
doc: make it clear contributors retain copyrights
TODO: removed Rainbows! (see rainbows.rubyforge.org)
Document the START_CTX hash contents
more-compatible TeeInput#read for POSTs with Content-Length
tests for read-in-full vs readpartial semantics
unicorn 0.93.2
 
D

Daniel Berger

Unicorn is a HTTP server for Rack applications designed to take
advantage of features in Unix/Unix-like kernels and only serve fast
clients on low-latency, high-bandwidth connections. =A0Slow clients shoul= d
only be served by placing a reverse proxy capable of fully-buffering
both the the request and response in between Unicorn and slow clients.

*http://unicorn.bogomips.org/
* (e-mail address removed)
* git://git.bogomips.org/unicorn.git

Thanks to Chris Wanstrath for reporting issues with large
POST bodies and for helping me test.

Changes:

Avoid truncated POST bodies with URL-encoded forms in Rails
by switching TeeInput to use read-in-full semantics (only) when
a Content-Length: header exists. =A0Chunked request bodies
continue to exhibit readpartial semantics to support
simultaneous bidirectional chunking.

The lack of return value checking in Rails to protect against a
short ios.read(length) is entirely reasonable even if not
pedantically correct. =A0Most ios.read(length) implementations
return the full amount requested except right before EOF.

A ticket has been opened here to track the issue:
=A0https://rails.lighthouseapp.com/projects/8994/tickets/3343

Also there are some minor documentation improvements.

Eric Wong (8):
=A0 =A0 =A0 Fix NEWS generation on single-paragraph tag messages
=A0 =A0 =A0 Include GPLv2 in docs
=A0 =A0 =A0 doc: make it clear contributors retain copyrights
=A0 =A0 =A0 TODO: removed Rainbows! (see rainbows.rubyforge.org)
=A0 =A0 =A0 Document the START_CTX hash contents
=A0 =A0 =A0 more-compatible TeeInput#read for POSTs with Content-Length
=A0 =A0 =A0 tests for read-in-full vs readpartial semantics
=A0 =A0 =A0 unicorn 0.93.2

There was a pretty good blog entry on Unicorn recently:

http://tomayko.com/writings/unicorn-is-unix

Regards,

Dan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,769
Messages
2,569,576
Members
45,054
Latest member
LucyCarper

Latest Threads

Top