On Tue, 7 Oct 2014, Scott Mitchell wrote:

>> $ curl --http2 --trace-ascii dump https://nghttp2.org/ --next --http2
>> https://nghttp2.org/ -d moo >/dev/null

> This is not the scenario I described. Let me summarize the scenario:

So such a command line works fine for you as well then?

I want a way to repeat the problem against a publicly accessible URL!

> I am building from github...what branch are you using?

We only really have a master branch so that's what I use.

> Is the nghttp2.org setup is a http/2 proxy infront of an nginx server?

I don't know the details about the nghttp2.org setup.

> If so it may be a good idea to get a http/2 only test setup to test the
> cases when the HTTP/1.x headers which are used for framing (i.e.
> content-length) can be excluded. That would make verifying this scenario
> works from a curl perspective easier ;)

A reasonable idea, yes. But I don't have any such server around...

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html