| Date | Commit message (Collapse) | ||
|---|---|---|---|
| 2010-07-19 | rev + em: more easily allow Content-Length in pipe responses | ||
| If a response proxying a pipe (or socket) includes a Content-Length, do not attempt to outsmart the application and just use the given Content-Length. This helps avoid exposing applications to weird internals such as env["rainbows.autochunk"] and X-Rainbows-* response headers. | |||
| 2010-07-19 | event_machine: avoid race in unchunked fast pipe responses | ||
| Using EM.enable_proxy with EM.attach seems to cause EM::Connection#receive_data callbacks to be fired before the proxy has a chance to act, leading the first few chunks of data being lost in the default receive_data handler. Instead just rely on EM.watch like the chunked pipe. | |||