unicorn is an HTTP server for Rack applications designed to only serve
fast clients on low-latency, high-bandwidth connections and take
advantage of features in Unix/Unix-like kernels. 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.
.onion URLs below are available for Tor users and can reduce
our operating costs:
* Index of /unicorn/
http://unicorn.ou63pmih66umazou.onion/
* public list: unicorn-public@yhbt.net
* mail archives: unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
http://ou63pmih66umazou.onion/unicorn-public/
* git clone unicorn.git - Rack HTTP server for Unix and fast clients
torsocks git clone http://ou63pmih66umazou.onion/unicorn.git
* unicorn news
http://unicorn.ou63pmih66umazou.onion/NEWS.atom.xml
* nntps://news.public-inbox.org/inbox.comp.lang.ruby.unicorn
nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.unicorn
imaps://news.public-inbox.org/inbox.comp.lang.ruby.unicorn.0
imap://ou63pmih66umazou.onion/inbox.comp.lang.ruby.unicorn.0
Changes:
unicorn 6.0.0 - no more recycling Rack env
This release allocates a new Rack `env' hash for every request.
This is done for safety with internally-(thread|event)-using Rack
apps which expect to use `env' after the normal Rack response is
complete, but without relying on rack.hijack[1]. Thanks to
Dirkjan Bussink <d.bussink@gmail.com> for the patch:
Re: Potential Unicorn vulnerability - Dirkjan Bussink
The major version is bumped since:
1) there are performance regressions for some simple Rack apps
2) unsupported 3rd-party monkey patches which previously
relied on this behavior may be broken (our version of
OobGC was).
The test suite is also more reliable on multi-core systems
and Ruby 3.x.