{"push_id":2500279234,"size":1,"distinct_size":1,"ref":"refs/heads/maintenance","head":"c6114848cbdc9f9b32d61044ec1dee3434d799a0","before":"168c7d24808bc44aec4f38b1201001c421df18c7","commits":[{"sha":"c6114848cbdc9f9b32d61044ec1dee3434d799a0","author":{"name":"Thiago Bustamante","email":"df68991a2292ce3b8a6bbee08027b8b26e48b9e2@gmail.com"},"message":"Fix \"Can't set headers after they are sent\" errors\n\nThis PR tries to fix \"Can't set headers after they are sent\" errors.\nThat are a lot of situations where this error can occurs. In my case, it is happening because I have others middlewares (in an expressjs application that tries to proxy requests). Some of those middlewares (like [passportjs](http://passportjs.org/), or [cors](https://www.npmjs.com/package/cors)) can run ```res.end()``` and when the proxy receive a response, it is already finished.\nSo, it is necessary to test if we can write on the user response when the proxy response is ready.\nI think it could also fix #930, #1168, #908","distinct":true,"url":"https://api.github.com/repos/nodejitsu/node-http-proxy/commits/c6114848cbdc9f9b32d61044ec1dee3434d799a0"}]}
{"actor":{"display_login":"jcrugzz"}}