From owner-freebsd-questions@FreeBSD.ORG Tue Jul 10 13:05:51 2012 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA76F106566B for ; Tue, 10 Jul 2012 13:05:51 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from kuller.raad.tartu.ee (kuller.raad.tartu.ee [213.184.43.8]) by mx1.freebsd.org (Postfix) with ESMTP id 84A168FC16 for ; Tue, 10 Jul 2012 13:05:51 +0000 (UTC) Received: from kuller.raad.tartu.ee (localhost [127.0.0.1]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 4689639822 for ; Tue, 10 Jul 2012 16:05:44 +0300 (EEST) X-Virus-Scanned: amavisd-new at post.raad.tartu.ee Received: from kuller.raad.tartu.ee ([127.0.0.1]) by kuller.raad.tartu.ee (kuller.raad.tartu.ee [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VQl3T5wu6L_7 for ; Tue, 10 Jul 2012 16:05:39 +0300 (EEST) Received: by kuller.raad.tartu.ee (Postfix, from userid 80) id 152783982E; Tue, 10 Jul 2012 16:05:39 +0300 (EEST) Received: from lv.raad.tartu.ee (lv.raad.tartu.ee [213.184.43.2]) by webmail.raad.tartu.ee (Horde Framework) with HTTP; Tue, 10 Jul 2012 16:05:39 +0300 Message-ID: <20120710160539.102922863js2qjs3@webmail.raad.tartu.ee> Date: Tue, 10 Jul 2012 16:05:39 +0300 From: Toomas Aas To: questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) X-Originating-IP: 213.184.43.2 Cc: Subject: curl error: SSL_write() returned SYSCALL, errno = 32 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2012 13:05:52 -0000 Hello! Recently I upgraded a lot of ports on one of our FreeBSD 7.4 servers. Among others I upgraded curl from 7.19.6 to 7.24.0, and php from 5.2.11 to 5.3.13. PHP's curl extension is also installed. After the upgrade, an application which tries to POST some data over https using PHP's curl_exec() function, is having trouble. curl_error() returns the following after the POST request: SSL_write() returned SYSCALL, errno = 32 Remote end to which the POST is submitted says simply "Invalid POST request" and they have told me that the request is truncated (content-length header does not match the actual content length). curl is installed with SSL support, using the base system OpenSSL. I tried to google for this error, but only thing that turns out is basically 'try to update curl', but I am already on latest. Any ideas on how to fix this or debug further? -- Toomas Aas