xfer: Ignore CURLE_AGAIN

This is happening when the server is sending a ping over WebSocket which
triggers the socket, but there is no data for us to deal with as it has
already been handled by cURL.

Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

diff --git a/src/libpakfire/xfer.c b/src/libpakfire/xfer.c
index c4e7c30164abc40520a4ebaa180d5378cf18fedc..a932872d6256df9c89b31c073ff4303485d6199c 100644 (file)
--- a/src/libpakfire/xfer.c
+++ b/src/libpakfire/xfer.c
@@ -925,6 +925,9 @@ static int pakfire_xfer_socket_recv(struct pakfire_xfer* xfer) {
                case CURLE_OK:
                        break;
 
+               case CURLE_AGAIN:
+                       return 0;
+
                // We seem to have lost the connection
                case CURLE_GOT_NOTHING:
                        return pakfire_xfer_fail(xfer, PAKFIRE_XFER_TRANSPORT_ERROR);