Unicorn 0.93.2 - more compatible with Rails

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.

Thanks to Chris W. 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 W. (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

On Oct 7, 3:00 am, Eric W. [email protected] wrote:

Thanks to Chris W. for reporting issues with large
The lack of return value checking in Rails to protect against a
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

Eric W.

There was a pretty good blog entry on Unicorn recently:

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

Regards,

Dan

Daniel B. [email protected] wrote:

On Oct 7, 3:00 am, Eric W. [email protected] wrote:

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.

There was a pretty good blog entry on Unicorn recently:

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

Yup, it is excellent :slight_smile:

One minor correction about SELF_PIPE usage here:

http://article.gmane.org/gmane.comp.lang.ruby.unicorn.general/59

Overall I’m extremely happy with the article and interest this has
generated in good ol’ Unix-isms :slight_smile:

On Oct 7, 4:15 pm, Eric W. [email protected] wrote:

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

Yup, it is excellent :slight_smile:

One minor correction about SELF_PIPE usage here:

http://article.gmane.org/gmane.comp.lang.ruby.unicorn.general/59

Overall I’m extremely happy with the article and interest this has
generated in good ol’ Unix-isms :slight_smile:

Here is some more:

http://jacobian.org/writing/star-is-unix/

Regards,

Dan

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs