Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
While the easy handle is definitely being added to the multi handle, and seeming to do things with the buffer, nothing is ever returned. Using
The only thing that I have noticed amiss is that the parent pointer as passed into the push callback is never returned from
I just verified that my test case against nghttpd still works fine though - using that same unaltered example code. What curl version are you using now?
For reference, I invoke my test server like this: https://github.com/bagder/curl-http2-dev/blob/master/run-nghttp2-push.sh
I suppose I might need to bite the bullet and get the node-http2 server up and see if I can reproduce with that one...
That sounds wrong. So what happens to that transfer? Does that simply never end?
@bagder using the test server you specified, the sample does work, but my own code does not. I'll look further into that.
WRT the parent point, another (different from
@bagder oops, I removed it. I have re-instantiated it. To run it, just clone the repo, then in
npm install node index.js
That will make it available on port 8080, which you can easily change on the last line of
It should return a simple bit of HTML, regardless of request:
Hello World! <script src="/main.js"></script>
And then pushes a file
alert("hello from push stream!")
If you hit this with nghttp on the command line, it works fine; however as noted, not through curl.