Stefan Eissing

You can send a URL to localhost with `curl --resolve curl-nego.neon.rocks:4433:127.0.0.1`. Then the hostname the server sees may work better for you.

@cuu508 thanks for the clarification. I can reproduce the RST with getting google's favicon over HTTPS. The reason is that curl tries to send a TLS shutdown *after* having seen...

@cuu508 this looks like an upload to a HTTP resource, not a GET. Just double checking...

Thanks. Looking at it again, curl seems to close the connection after having send the GET request, causing all response data from the server to result in RST. Is it...

The key lines here are: ``` 11:35:39.759759 [0-0] * Failure writing output to destination, passed 691 returned 4294967295 11:35:39.759796 [0-0] * Closing connection ``` meaning that curl encountered an error...

Please let's not switch the things we investigate before we are done knowing what is going on. Could you verify how the following command works in your setup? ``` SSLKEYLOGFILE=/tmp/tls/secrets.log...

Thanks. Just to explain: if curl encounters an error on its side, like writing binary to the terminal, it aborts the transfer. If the server is still sending at that...

Thanks @cuu508 ! I tested that and pushed an improvement to #13087. Would be nice if you could verify this.

> @icing can you take a look at the merge conflict here? @bagder rebased.

Rebased again after the curldown nuke.