Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <31296974.143271275511177596.JavaMail.jira@thor>
Date: Wed, 2 Jun 2010 16:39:37 -0400 (EDT)
From: "Jan Lehnardt (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Closed: (COUCHDB-385) responses to HEAD requests for
 _all_docs* have bogus "Content-Length: 0" header
In-Reply-To: <937874490.1245187447349.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Lehnardt closed COUCHDB-385.
--------------------------------

    Resolution: Cannot Reproduce

Cannot reproduce in 0.11.x. Please reopen if this still persists. Ideally with a JavaScript test case.

> responses to HEAD requests for _all_docs* have bogus "Content-Length: 0" header
> -------------------------------------------------------------------------------
>
>                 Key: COUCHDB-385
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-385
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 0.9
>         Environment: Linux melkjug.org 2.6.26-hardened-r4 #2 SMP Fri Oct 24 00:59:43 AKDT 2008 x86_64 Intel(R) Xeon(R) CPU L5430 @ 2.66GHz GenuineIntel GNU/Linux
>            Reporter: Joshua Bronson
>
> CouchDB invariably sends a bogus "Content-Length: 0" header in response to HEAD requests for _all_docs and _all_docs_by_seq (and possibly other queries). According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4 "The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request."
> (I discovered this while writing a python script to stream the body of an _all_docs_by_seq response to stdout for use as a database dump.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.