>First, --next does not (necessarily) make an other connection. It makes another transfer and that transfer can re-use a connection or create a new one.

How can I force curl to re-use a connection (specifically in http2 mode)?

>Then, I don't see any good motivation why --next would impose some special magic on which stream the next request to be done over, as that's a very specific HTTP/2 implementation detail. What's your motivation for wanting a new stream on demand?

Re-using a connection is the motivation. As I understand it this was one of the primary reasons HTTP/2 was developed. You are welcome to make a new feature to accomplish this if it makes more sense, --next just seemed to naturally lend itself to this.

>Finally: as far as my reading of the http2 spec goes, isn't all new requests over the same physical connection going to use a new stream anyway?

Yes. This is the point. I would like to re-use a connection to issue multiple requests which should result in a new stream for each request. Is there a way to do this today?

---
** [bugs:#1428] make http/2 --next use a new stream**
**Status:** pending-needsinfo
**Labels:** http2 
**Created:** Mon Sep 29, 2014 02:39 PM UTC by Scott Mitchell
**Last Updated:** Thu Oct 02, 2014 07:03 AM UTC
**Owner:** Daniel Stenberg
The --next flag for HTTP/2 does not result in requests on a new stream (when --next URL is the same as previous URL).  Instead it looks like curl is attempting to open a new connection which results in SSL connection error (like the following):
>SSL/TLS handshake error error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.