From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id C8470430D5B for ; Mon, 28 Oct 2019 20:11:21 +0300 (MSK) From: Ilya Kosarev Date: Mon, 28 Oct 2019 20:11:15 +0300 Message-Id: <9cdb220e73e142d85ef536c0b27a20180f8f7088.1572282336.git.i.kosarev@tarantool.org> In-Reply-To: References: In-Reply-To: References: Subject: [Tarantool-patches] [PATCH v4 4/4] http: add CURLE_BAD_CONTENT_ENCODING case for curl_request code List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: tarantool-patches@freelists.org Cc: tarantool-patches@dev.tarantool.org Currently in case of unknown encoding curl returns CURLE_WRITE_ERROR request code. Since curl/curl#4449 CURLE_BAD_CONTENT_ENCODING request code will be returned in this case. Therefore mentioned case has to be added into switch clause processing curl request code. Closes #4579 --- src/httpc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/httpc.c b/src/httpc.c index b493a8498..d3516049e 100644 --- a/src/httpc.c +++ b/src/httpc.c @@ -447,6 +447,7 @@ httpc_execute(struct httpc_request *req, double timeout) case CURLE_COULDNT_RESOLVE_HOST: case CURLE_COULDNT_CONNECT: case CURLE_WRITE_ERROR: + case CURLE_BAD_CONTENT_ENCODING: /* 595 Connection Problem (AnyEvent non-standard) */ req->status = 595; req->reason = curl_easy_strerror(req->curl_request.code); -- 2.17.1