Nicholas Hurley

So I get that node's https module allows this, but how many things does not having this functionality break? In reality, it makes zero sense to have a server with...

Thanks, @felicienfrancois for the added context. I got to thinking about this more last night (even before you commented), and what I think we should do is this - remove...

I can see the use case for this, but I'd rather spend what limited time I have for this module on fixing actual bugs. I'm going to leave this open,...

I'm sure it is. However, it's low priority. I would gladly accept a patch that added them, though.

Why do you want to close the client? The entire point of http/2 is that you don't have to keep opening connections. (Not saying having an option to close is...

This needs a lot more information - how much slower? Are there any pulled streams being served at the same time as a push? If so, does the pushed stream...

This sounds like a possible bug - do you have an example?

There is currently no way in the http/2 client code to notice GOAWAY/INADEQUATE_SECURITY (at least, no easy way). This would be a decent enhancement/feature, but not a high-priority one.

First off, yes, this is a bug. However - you shouldn't be manually closing down sockets with HTTP/2. If you wish to not respond to a request, you should instead...

The request object will hang around, so just ignoring things isn't exactly suggested (unless you're ignoring them until a certain point in the future), but it won't break communication immediately...