On 2013-09-13 11:41, Daniel Stenberg wrote:
> On Fri, 13 Sep 2013, Mehmet Bozkurt wrote:
>
>> The original issue was posted here (actually this link is the last
>> reply in the thread and contains the fix proposal):
>> http://curl.haxx.se/mail/lib-2009-11/0191.html
>
> We get a fair amount of such issues sent to us, I provide a fair amount
> of suggested solutions to such issues. When I don't get enough feedback
> or if nobody reminds me, it happens that I forget them or just leave
> them behind (due to lack of interest from others than me for example) as
> I move on. I don't recall how this particular issue turned out to not
> get merged.
>
> ...
>
>> So what I'm asking is if libcurl handles SSL_ERROR_WANT_READ/WRITE by
>> calling the same OpenSSL method that caused the error return or is the
>> strategy still as in the old version; libcurl makes a call based on
>> whatever select() returns?
>
> Given a quick glance, I would say the latter. But then as you say you
> can't repeat the problem it might also explain why nobody else has
> reported this to be a problem...
>

I understand, just curious to know if there were some particular reason
as to why it didn't get merged. Safest for us would be to keep the patch
if we decide to upgrade our libcurl version.

Many thanks for your input!

/Mehmet
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-09-13