Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Thu, 7 Apr 2011 18:26:06 +0000 (UTC)
From: "Jyrki Pulliainen (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1163894335.41806.1302200766012.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (COUCHDB-1123) Longpolling changes feed with
 filter and accidental Content-Length header stalls
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Longpolling changes feed with filter and accidental Content-Length header stalls
--------------------------------------------------------------------------------

                 Key: COUCHDB-1123
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1123
             Project: CouchDB
          Issue Type: Bug
          Components: HTTP Interface
    Affects Versions: 1.0.2
         Environment: Mac OS X Snow Leopard, Ubuntu 10.10.
            Reporter: Jyrki Pulliainen
            Priority: Minor


CouchDB behaves erroneously when doing a GET request with Content-Length header to long polling changes feed with filter set.

Easiest way to reproduce:
1. Create a new DB
2. Create a single design doc with a filter that just returns true
3. Query database with curl: curl -v -H "Content-Length: 123" http://localhost:5984/database/_changes?feed=longpoll&filter=designdoc/filter

At this point CouchDB behaves strangely. It does not wait for the client to feed the Content-Length bytes of content (which I think is correct, since GET should not have payload), instead, it returns 200 OK and starts the response with '{"results":['. However, no changes done to database ever get emitted and the connection never gets closed, not even if explicit timeout is set upon the request.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira