- **status**: pending-needsinfo --> closed-invalid
- **Comment**:

This is not a bug but has turned into a support issue or series of issues. This is detailed in the curl man page and if you need general help on how to use the curl too, the curl-users mailing list is there. I consider this case closed.

---
** [bugs:#1428] make http/2 --next use a new stream**
**Status:** closed-invalid
**Labels:** http2 
**Created:** Mon Sep 29, 2014 02:39 PM UTC by Scott Mitchell
**Last Updated:** Fri Oct 03, 2014 04:18 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.