Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 96568 invoked from network); 23 Apr 2008 09:23:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Apr 2008 09:23:12 -0000 Received: (qmail 72592 invoked by uid 500); 23 Apr 2008 09:23:14 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 72557 invoked by uid 500); 23 Apr 2008 09:23:13 -0000 Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-user@incubator.apache.org Delivered-To: mailing list couchdb-user@incubator.apache.org Received: (qmail 72546 invoked by uid 99); 23 Apr 2008 09:23:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 02:23:13 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.41.228.50] (HELO mail.inqnet.at) (212.41.228.50) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 09:22:22 +0000 Message-ID: <480EFFF0.3050106@iworks.at> Date: Wed, 23 Apr 2008 11:22:56 +0200 From: Michael Wallner User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: couchdb-user@incubator.apache.org Subject: Re: Missing HTTP/1.1 0 Trailer References: <480D9B51.7040408@iworks.at> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Benoit Chesneau wrote: > It seem that http/1.1 response is ok here. I simply tested it with a > script hat send put/post and get regest and always have the right > answerI. Ie a chunk followed by O\r\n which is a valid http/1.1 > response. Is there any specific case you didn't get a valid response ? I just discoverd that it depends on libcurls standard "Expect: 100 continue" header sent on POST(/PUT?). Either libcurl is confused by how CouchDB reacts on this header, or CouchDB is confused... not sure yet. Forcing libcurl to not send the Expect header vanishes the problem, but I'm not sure this is the best solution. Thanks, Mike