search

spdy-http2 / node-spdy

SPDY server on Node.js
2.81k stars 196 forks source link

Chrome 24 only receives partial content #71

Closed ajacksified closed 11 years ago

ajacksified commented 11 years ago

I'm not sure if this is a Chrome bug, a node-spdy bug, or an express bug. Details:

I only receive the first 50 lines or so of html, and then page rendering stops. It works fine, with spdy/3, in Firefox 18.1.

Let me know if I can provide anything else.

Screen Shot 2013-01-23 at 5 22 13 PM

indutny commented 11 years ago

HEAD works only with node.js 0.9.x right now, so I guess you was using 1.3.9 version. Can you please give me more details like reduced test case?

ajacksified commented 11 years ago

I'll get an example and see if I can get it to fail again; weirdly, it started behaving properly today. I have a vague feeling that it has something to do with me banging around with net-internals.

indutny commented 11 years ago

Ok. I'll close this issue for now, please feel free to reopen it if you'll be able to reproduce it again!

And thank you for reporting it!

ajacksified commented 11 years ago

Alright, reproduced again just now. I made a test repo: https://github.com/ajacksified/node-spdy-test

(note: this version uses node-spdy 1.4.0)

I suppose it could also be an express issue. Lots of moving parts. It seems like it works on the first request, but hangs afterwards. Restarting node and Chrome doesn't appear to fix things. It only appears to happen in Chrome.

Also, this time it doesn't appear to send partial content anymore, but hangs the request. Forever loading for all files:

Screen Shot 2013-01-24 at 1 44 58 PM

Update: I also unchecked enable experimental spdy/3 from chrome://flags to no effect. Update 2: tried another macbook with the same Chrome version, experiencing the same thing. Update 3: tried with windows 7 with Chrome 24.0.1312.56, same symptoms. Update 4: same thing with OSX / 26.0.1386.0 dev Update 5: providing content with spdy createserver instead of express results in success, leading me to believe it's either express or a problem with spdy responding to multiple requests and closing appropriately.

ajacksified commented 11 years ago

Express HEAD (https://github.com/visionmedia/express/tree/03a796c4604a031cf729d3cac7bf38ee99f3e74b) fixes my demo, but does not fix my main app, which spins forever, although all network requests appear completed. I'll try to update my demo to recreate the problem.

indutny commented 11 years ago

I did some fixes in @1.4.2, can you please try it and report result here?

ajacksified commented 11 years ago

That appears to have fixed it! I'm not seeing any more hangs.

indutny commented 11 years ago

Great! Closing issue, thanks for reporting.