Stefan Eissing

Thanks for the advice. Will try that in curl.

@bagder we could replace the stack buffers with allocated ones, using `data->set.buffer_size`. They need to only exist for the duration of the loops, directly freed again. If you like that,...

I made #12932 which uses the multi's transfer buffer for file: operations. This should restore the buffer sizes and behaviour exactly as it was in curl 8.5.0.

@HsiehYuho I added a test case using '127.0.0.1' for the proxy and gave it a certificate with a x590 IPAddress in the alt names. This test works with curl 8.6.0....

@knekritz, @HsiehYuho thanks, that is exactly the right spot. Would you be able to verify that #12931 fixes the issue for you as well?

@HsiehYuho if you run ./src/curl with options `-v --trace-config all` and your other arguments, what is the output?

@dkarpov1970 If I understand you correctly, the application does a "connect only", getting the socket from curl and then reading/writing to that socket directly. When it is done, it calls...

> I think I found a not over complicated sequence that can reproduce the crash with HTTPs transfer done via curl_easy_perform(), socket closure and post transfer SSL read: > >...

@dkarpov1970 Thanks for the reminder. Question: would `curl_easy_recv()` not be the right way to read more from the connection? I still don't like the idea that apps do I/O on...

> Yes, the `SSL_read` is done by the application after having extracted the SSL handle/context from the connection libcurl. > > But the app developers told me that they can't...