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
