diff options
author | Eric Wong <normalperson@yhbt.net> | 2009-10-16 13:46:18 -0700 |
---|---|---|
committer | Eric Wong <normalperson@yhbt.net> | 2009-10-16 13:54:57 -0700 |
commit | 580d242fbfe95ea2ce7709f90f25e655bc2d93ac (patch) | |
tree | 19dd8da1e1f3d3d346a042bf0470b9af17b6e914 /KNOWN_ISSUES | |
parent | 370cb0670d1b1841ae19e871e7aee4fec167d4e8 (diff) | |
download | unicorn-580d242fbfe95ea2ce7709f90f25e655bc2d93ac.tar.gz |
In short: upgrade to Rails 2.3.4 (or later) ref: http://mid.gmane.org/20091014221552.GA30624@dcvr.yhbt.net Note: the workaround described in the article above only made the issue more subtle and we didn't notice them immediately.
Diffstat (limited to 'KNOWN_ISSUES')
-rw-r--r-- | KNOWN_ISSUES | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/KNOWN_ISSUES b/KNOWN_ISSUES index 436997d..979ac9d 100644 --- a/KNOWN_ISSUES +++ b/KNOWN_ISSUES @@ -1,5 +1,18 @@ = Known Issues +* Rails 2.3.2 bundles its own version of Rack. This may cause subtle + bugs when simultaneously loaded with the system-wide Rack Rubygem + which Unicorn depends on. Upgrading to Rails 2.3.4 (or later) is + strongly recommended for all Rails 2.3.x users for this (and security + reasons). Rails 2.2.x series (or before) did not bundle Rack and are + should be unnaffected. If there is any reason which forces your + application to use Rails 2.3.2 and you have no other choice, then + you may edit your Unicorn gemspec and remove the Rack dependency. + + ref: http://mid.gmane.org/20091014221552.GA30624@dcvr.yhbt.net + Note: the workaround described in the article above only made + the issue more subtle and we didn't notice them immediately. + * Installing "unicorn" as a system-wide Rubygem and using the {isolate}[http://github.com/jbarnette/isolate] gem may cause issues if you're using any of the bundled application-level libraries in |