Yes, I may use CLOSESOCKETFUNCTION, but even then I have to do the trick delaying the actual close() call. Otherwise, as I already said, I get CURL_POLL_REMOVE notification for already closed socket. And really bad thing is that a new socket or other thing may be opened (in other thread) and takes over the old FD number. Even worse is if that new thing is added to the same network reactor used for curl.

---
** [bugs:#1355] Socket callback with CURL_POLL_REMOVE is too late**
**Status:** open
**Created:** Mon Apr 07, 2014 10:08 PM UTC by Constantin Baranov
**Last Updated:** Tue Apr 08, 2014 07:31 AM UTC
**Owner:** Daniel Stenberg
Sometimes curl closes a socket before notifying user via SOCKETFUNCTION. I caught this in a case when I want to terminate a transfer in the middle of downloading.
See attached source. I'd expect fcntl() don't fail. If it doesn't work (i.e. doesn't report fcntl error), change the URL to a bigger resource.
I'd like to let curl close its sockets, but I need to get CURL_POLL_REMOVE message when socket is still alive. Otherwise my network reactor goes crazy.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.