So the issue is really a feature request. The --next option for HTTP/2 is opening a new socket for each request. The feature request is to use a new stream (instead of opening a new connection) when the request URLs make sense to do so.

---
** [bugs:#1428] http/2 --next error**
**Status:** pending-needsinfo
**Labels:** http2 
**Created:** Mon Sep 29, 2014 02:39 PM UTC by Scott Mitchell
**Last Updated:** Tue Sep 30, 2014 09:40 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.