Alan Chandler

My, rather simplistic solution (meaning I don't get all the extras from `serve-static`) was to use this to serve my static files ``` //simple serve-static function staticFiles (cpath) { const...

@MichaelSun90 you have it about right, I just wrap things in promises, I decided to write a little test harness to test this. However I am finding that even the...

My work around ``` if (err) { if (err.code === 'ESOCKET') { logger('error', 'Tedious connection failed with socket failure, so we are exiting'); process.kill(process.pid, "SIGINT"); //kill ourselves } else {...

are you aware that node 8.4.0 now has experimental http2 support behind a --expose-http2 flag. It is much faster as it relies on nghttp2 under the hood which is native...

I get this too. I though at first it was related to using push, where I sent a lot of files one after the other (about 40) but it has...

I discovered what this was and its NOT a memory leak. Its the way serve-static handles streams. I've actually just raised this as an issue against that repository https://github.com/expressjs/serve-static/issues/87

I have found a workaround for this which is showing some interesting results. In particular, I am failing on one specific file, which is supposed to being loaded as a...

I have been conducting some tests with different browsers to see where things are. I have altered my application so I can switch push on and off with a simple...

I have skirted this issue in the tests I created to fix #161 by using a different port number. I think it must be the use of a global agent,...

After discovering several issues with app-route, this being one of them I ended up implementing an alternative. I am not particularly promoting this here, but you can find it on...