Non of the code runs in chapter 11 (Can't set headers after they are sent)

還沒有人認領這個 Issue。

If you try running any code in chapter 11 you get the same error "Can't set headers after they are sent"

Express 3.0.0beta7
CoffeeScript version 1.3.3
Node v0.8.2

http.js:644
throw new Error('Can\'t set headers after they are sent.');
^
Error: Can't set headers after they are sent.
at ServerResponse.OutgoingMessage.setHeader (http.js:644:11)
at ServerResponse.res.setHeader (/Users/work/todo/node_modules/express/node_modules/connect/lib/patch.js:62:20)
at ServerResponse.res.header (/Users/work/todo/node_modules/express/lib/response.js:280:8)
at ServerResponse.res.json (/Users/work/todo/node_modules/express/lib/response.js:135:8)
at Create.global.Responder.Responder.complete (/Users/work/todo/src/controllers/responders/responder.js:27:25)
at Promise.__bind (/Users/work/todo/src/controllers/responders/responder.js:3:63)
at Promise.addBack (/Users/work/todo/node_modules/mongoose/lib/promise.js:120:8)
at Promise.EventEmitter.emit (events.js:88:17)
at Promise.emit (/Users/work/todo/node_modules/mongoose/lib/promise.js:59:38)
at Promise.complete (/Users/work/todo/node_modules/mongoose/lib/promise.js:70:20)

先使用列出的 CoffeeScript、Express 和 Node 版本執行第 11 章中的一個範例，接著將回報的失敗追蹤到 src/controllers/responders/responder.js。比較第 11 章的其他範例，以判斷它們是否到達相同的 responder path；完成的標準是章節範例能夠執行且不會出現回報的 headers error。

由索引模型根據 Issue 內容生成。