cURL cURL > Mailing List > Monthly Index > Single Mail

curl-tracker Archives

[curl:bugs] #1428 make http/2 --next use a new stream

From: Scott Mitchell <scottmitch3_at_users.sf.net>
Date: Fri, 03 Oct 2014 16:18:14 +0000

I think I'm getting closer to what I'm trying to do with your help ;). Is there a way to set 2 different POST request bodies for each request?

For example I have tried the following:
>$ curl -i --http2 -k 'https://10.0.2.2:13443/proxy/address' -H "accept: application/vnd.akamai.query" -d '<json object>' 'https://10.0.2.2:13443/sql' -d '<opaque data>'

However I'm seeing some strange behavior. I'm seeing 2 connections being made. The first connection appears to correctly open 2 streams (one for each request with the first stream using the HTTP upgrade stream) however the POST request body seems to be combined as `<json object>&<opaque data>` for both requests. The second connection just has 1 stream which corresponds to the second URL (`/sql`) but again with POST body being a combination of the two.

---
** [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 02:42 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.
Received on 2014-10-03

These mail archives are generated by hypermail.