# Unicorn 0.8.4

**URL:** <https://www.ruby-forum.com/t/unicorn-0-8-4/173334>\
**Category:** Ruby\
**Created:** [August 7, 2009, 1:08am UTC](https://www.ruby-forum.com/t/unicorn-0-8-4/173334 "2009-08-07T01:08:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ericw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/97f17d/32.png) [@ericw](https://www.ruby-forum.com/u/ericw)\
**Post date:** [August 7, 2009, 1:08am UTC](https://www.ruby-forum.com/t/unicorn-0-8-4/173334/1 "2009-08-07T01:08:50Z")

</div>

Unicorn is a Rack HTTP server for Unix, fast clients and nothing else

This release allows graceful degradation in case a user is using a  
status code not defined by Rack::Utils::HTTP\_STATUS\_CODES. A patch has  
been submitted[1] upstream to Rack but this issue may still affect users  
of yet-to-be-standardized status codes.

- site: [http://unicorn.bogomips.org/](http://unicorn.bogomips.org/)
- git: git://git.bogomips.org/unicorn.git
- cgit: [Rack HTTP server for Unix and fast clients](http://git.bogomips.org/cgit/unicorn.git/)
- list: removed\_email\_address@domain.invalid

[1] - [http://rack.lighthouseapp.com/projects/22435-rack/tickets/70](http://rack.lighthouseapp.com/projects/22435-rack/tickets/70)

There is no 0.9.x release of Unicorn planned to fix this issue,  
I’m too tired at the moment and 0.9.x is an experiment anyways.