Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: ALPN - HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Robert Wolf via curl-users <curl-users_at_lists.haxx.se>
Date: Tue, 12 Jul 2022 12:02:23 +0200
Dear Daniel,
You were right, the --no-alpn was only coincidence - curl use HTTP/1.1 with
--no-alpn. Forcing http2 with --no-alpn using --http2 --http2-prior-knowledge
results to the same issue
HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
I did tcpdump and saved the keys. I have one dump from curl and one dump from
firefox (if you want to compare tls and http2). The website is protected with
SSO OIDC so you cannot test it yourself.
But I would like to keep the files private. They do not contain sensitive data,
but I don't even want to share these dumps with the PDF file from the our
server, because I'm not sure, how sensitive the file is. Would it be possible
to share these file privately with you and only with other developers, who need
to see them to fix the code or analyze the communication? Keys and both
tcpdumps are about 750kB. May I send it per email or do you have any
secure/private storage?
We can then create issue on github without data if you find out if this is
curl or server bug.
Would it be possible to do it this way?
Thank you very much for your help.
Regards,
Robert Wolf.
On Sat, 9 Jul 2022, Daniel Stenberg wrote:
> On Wed, 6 Jul 2022, Robert Wolf via curl-users wrote:
>
> >> And it would also help if you could record a failing HTTP/2 TCP stream with
> >> wireshark.
> >
> > Where can I save or how can I send you the tcpdumps? May I send them to your
> > private address? I have made one with alpn and one without.
>
> As that traffic was done over HTTPS, did you also provide the keys so that
> wireshark could descrypt and analyze the h2 frames? Otherwise the pcaps won't
> help us much.
>
> You can create an issue on github and attach the files there:
>
> https://github.com/curl/curl/issues
>
> --
>
> / daniel.haxx.se
> | Commercial curl support up to 24x7 is available!
> | Private help, bug fixes, support, ports, new features
> | https://curl.se/support.html
>
>
Date: Tue, 12 Jul 2022 12:02:23 +0200
Dear Daniel,
You were right, the --no-alpn was only coincidence - curl use HTTP/1.1 with
--no-alpn. Forcing http2 with --no-alpn using --http2 --http2-prior-knowledge
results to the same issue
HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
I did tcpdump and saved the keys. I have one dump from curl and one dump from
firefox (if you want to compare tls and http2). The website is protected with
SSO OIDC so you cannot test it yourself.
But I would like to keep the files private. They do not contain sensitive data,
but I don't even want to share these dumps with the PDF file from the our
server, because I'm not sure, how sensitive the file is. Would it be possible
to share these file privately with you and only with other developers, who need
to see them to fix the code or analyze the communication? Keys and both
tcpdumps are about 750kB. May I send it per email or do you have any
secure/private storage?
We can then create issue on github without data if you find out if this is
curl or server bug.
Would it be possible to do it this way?
Thank you very much for your help.
Regards,
Robert Wolf.
On Sat, 9 Jul 2022, Daniel Stenberg wrote:
> On Wed, 6 Jul 2022, Robert Wolf via curl-users wrote:
>
> >> And it would also help if you could record a failing HTTP/2 TCP stream with
> >> wireshark.
> >
> > Where can I save or how can I send you the tcpdumps? May I send them to your
> > private address? I have made one with alpn and one without.
>
> As that traffic was done over HTTPS, did you also provide the keys so that
> wireshark could descrypt and analyze the h2 frames? Otherwise the pcaps won't
> help us much.
>
> You can create an issue on github and attach the files there:
>
> https://github.com/curl/curl/issues
>
> --
>
> / daniel.haxx.se
> | Commercial curl support up to 24x7 is available!
> | Private help, bug fixes, support, ports, new features
> | https://curl.se/support.html
>
>
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-07-12