about summary refs log tree commit homepage
path: root/lib/rainbows/http_response.rb
DateCommit message (Collapse)
2010-07-19refactor response handling for each concurrency model
This will give each concurrency model more control over particular code paths and serving static files.
2010-07-10doc: avoid documenting internals on RDoc website
Since we suck at building websites, we just rely on RDoc as a website builder. And since Rainbows! is an application server (and not a programming library), our internal API should be of little interest to end users. Anybody interested in Rainbows! (or any other project) internals should be reading the source.
2010-07-09http_response: allow Cramp 0.11 to send proper WS headers
Cramp needs to override our normal header sending for (old) WebSockets connections.
2010-07-08restore Rainbows::HttpResponse.write for Cramp
Cramp monkey patches Rainbows internals for WebSockets support and we forgot about it. Add a new integration test to ensure this continues to work in the future (and force us to update the test for newer Cramp).
2010-07-04refactor response body handling for sendfile(2)
This hopefully allows the "sendfile" gem to be required anywhere in the Rainbows!/Unicorn config file, and not have to be required via RUBYOPT or the '-r' command-line switch. We also modularize HttpResponse and avoids singleton methods in the response path. This (hopefully) makes it easier for individual concurrency models to share code and override individual methods.
2010-06-27http_response: make this a module, not a class
No point in using a class here, there's no object
2010-06-27http_response: (nitpick) simplify conditional logic
2010-06-27http_response: cleanup documentation
No point in documenting our internals and overwhelming users.
2010-04-19http_response: split out header stringification code
This will make it easier to use body#to_path if possible since some concurrency models like EventMachine have optimized code paths for serving static files.
2010-04-02rainbows/http_*: remove unnecessary circular requires
http_response and http_server are never NOT loaded when "rainbows" is required.
2010-01-05http_response: disallow blank, multi-value headers
The HeaderHash optimizations in Rack 1.1 interact badly with Rails 2.3.5 (and possibly other frameworks/apps) which set multi-value "Set-Cookie" headers without relying on the proper methods provided by Rack::Utils. While this is an issue with Rails not using properly, there may be similar apps that make this mistake and Rack::Lint does not guard against it. Rack-ML-Ref: <20100105235845.GB3377@dcvr.yhbt.net>
2009-11-10http_response: don't "rescue nil" for body.close
This can hide bugs in Rack applications/middleware. Most other Rack handlers/servers seem to follow this route as well, so this helps ensure broken things will break loudly and more consistently across all Rack-enabled servers.
2009-10-18http_response: filter out X-Rainbows-* headers
We'll be using some custom headers to craft responses
2009-10-02initial revision
No tests yet, but the old "gossamer" and "rainbows" branches seem to be basically working.