The patch works for me (I applied the changes to Mongoose 5.5). Thank you.

Am Montag, 16. Februar 2015 19:34:33 UTC+1 schrieb Sergey Lyubka:
>
> Thanks Sebastian.
> Pushed 
> https://github.com/cesanta/mongoose/commit/44a146faf6423729a2d0e873d872f609687a01f6
> Could you confirm it works for you, please?
>
> On Thu, Jan 15, 2015 at 9:53 AM, <sebastian...@googlemail.com 
> <javascript:>> wrote:
>
>> Hello,
>>
>> I had a related issue. On a SSL encrypted connection using keep-alive 
>> became unresponsive after receiving a large response. The response was 
>> received correctly, but sending a new request over the open connection did 
>> not result in any answer. Investigating further, I found the connection was 
>> not added to read_set in ns_mng_poll, because NSF_WANT_WRITE was still set. 
>> Applying the patch solved the problem. Thank you Nikos.
>>
>> Maybe this should be included into Mongoose/NetSkeleton
>>
>> Regards
>> Sebastian Puschhof
>>
>> Am Dienstag, 6. Januar 2015 14:23:22 UTC+1 schrieb Nikos:
>>
>>> Hello,
>>>
>>> While trying mongoose 5.5 and SSL under Linux, I believe I came across 
>>> the following issue, which manifested itself (if I remember correctly) as 
>>> unresponsive web browser connections and reception of partial data (both 
>>> chrome & firefox).
>>>
>>> When a SSL_read/SSL_write method triggers an 
>>> SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE error, the 
>>> NSF_WANT_READ/NSF_WANT_WRITE flags are set appropriately. However, when the 
>>> error is subsequently resolved by another SSL_* operation, the NSF_WANT_* 
>>> flags are not reset to their neutral state. As a result, the aborted 
>>> operation does not resume.
>>>
>>> I am attaching the change that resolved the issue for me, in order to 
>>> further clarify. Is this a genuine issue or am I misusing mongoose somehow?
>>>
>>> Thank you,
>>> Nikos
>>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "mongoose-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to mongoose-user...@googlegroups.com <javascript:>.
>> To post to this group, send email to mongoos...@googlegroups.com 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/mongoose-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"mongoose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mongoose-users+unsubscr...@googlegroups.com.
To post to this group, send email to mongoose-users@googlegroups.com.
Visit this group at http://groups.google.com/group/mongoose-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to