Closed nodeIntegrator closed 8 years ago
I'm afraid res.push
is available only for SPDY streams, so if browsers does request to a plain-mode server - it'll use HTTP. Thus, there won't be a res.push
.
Guess, this is an example bug. I'd appreciate if someone will fix it ;)
So, as a newbie to this, maybe I am going about this the wrong way... What is the right configuration for doing SSL termination separately (using NGINX, stud, apache, etc.) where I unwrap HTTPS and proxy to node-spdy?
@nodeIntegrator you need to advertise SPDY support in NPN if you want to use plain
mode. AFAIK, stud does not support it out-of-the-box. However we added support to it at Voxer:
You could also consider giving a try to: https://github.com/indutny/bud, which does support it quite well.
Ahhh, it all makes sense now. I hadn't put together the idea that the NPN support would need to be on the SSL termination side (though it is obvious now). Thanks for the clarification.
I will give those options a shot.
So, I have been trying to get the examples to work, but in plain mode, by making the below changes.
I test it using
spdycat -nv -3 [my url]
, and it works fine.But if I try to use it with any browser or the okHttp java library, it crashes the app with this:
I have tried several versions of the library and similar examples, none work.
I feel like I am missing something fundamental about this module and perhaps the protocol, but I worry about using the module if it is this brittle (someone with the wrong browser crashing the server).
Obviously, the examples aren't exactly production code, and I don't mean to be too sharp with my criticism, but any available insight is greatly appreciated.