- **summary**: http/2 --next error --> make http/2 --next use a new stream
- **Comment**:

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.

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?

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?

---
** [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:** Wed Oct 01, 2014 06:47 PM 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.