Closed jescalan closed 9 years ago
Are you getting a 200 response with 0 bytes?
@scottcorgan yupp
In a beta version of Superstatic, we are seeing the same thing. I'll reference when we see what's up.
On Fri, Aug 29, 2014 at 12:32 PM, Henry Snopek notifications@github.com wrote:
@scottcorgan https://github.com/scottcorgan yupp
— Reply to this email directly or view it on GitHub https://github.com/carrot/charge/issues/23#issuecomment-53920501.
Awesome, glad to have a little help here! This bug is pretty rough, really makes it impossible to use in production. We'll let you know if we find anything as well.
I'm sorry, I totally don't understand your response at all... could you give me a little more context?
I'm going to assume it doesn't apply to Charge in that this is a proxy portion of Superstatic.
Just wanted to give you a place to start looking. Namely the areas that use res.statusCode
.
Ah ok, will look around spots that use res.statusCode
then -- thanks!
So we have known about this for a bit, but occasionally when running in production, the server stops actually serving requests and just sends back blank pages. This is very strange, and we should figure out what's causing it.