1.3.0 features a bug that makes Sinatra 1.3.3 (probably also other Rack based applications) to crash whenever a conditional request with the header If-Modified-Since is addressed at the server, at least for public files but probably for any file under cache-control.
1.3.1 solves this issue, apparently just fine, but because of bundler updating my gems to a specific set when a Gemfile.lock was generated, many pcs in my office got "infected" with version 1.3.0, causing all of them to feature this hard-to-debug error in Sinatra when we ran Ruby without Bundler. It will be nice to yank 1.3.0 from rubygems.org so bundler autoupdates the locked versions and no one else faces this strange error.
rkh
commented
11 years ago
1.3.0 features a bug that makes Sinatra 1.3.3 (probably also other Rack based applications) to crash whenever a conditional request with the header
If-Modified-Sinceis addressed at the server, at least for public files but probably for any file under cache-control.1.3.1 solves this issue, apparently just fine, but because of bundler updating my gems to a specific set when a Gemfile.lock was generated, many pcs in my office got "infected" with version 1.3.0, causing all of them to feature this hard-to-debug error in Sinatra when we ran Ruby without Bundler. It will be nice to yank 1.3.0 from rubygems.org so bundler autoupdates the locked versions and no one else faces this strange error.
Thanks :)