couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damjan Georgievski (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-1852) Last-Event-ID header should be honoured in eventsource _changes feed
Date Mon, 15 Jul 2013 10:46:48 GMT


Damjan Georgievski updated COUCHDB-1852:

    Attachment: 0002-Fix-for-COUCHDB-1852.patch

Here's the latest patches. I checked that the test fails for non-patched couch_httpd_db and
succeeds on a patched one.

I don't know if I can make the tests fail with a more reasonable error message?
> Last-Event-ID header should be honoured in eventsource _changes feed
> --------------------------------------------------------------------
>                 Key: COUCHDB-1852
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>            Reporter: Damjan Georgievski
>         Attachments: 0001-make-test-for-COUCHDB-1852.patch, 0002-Fix-for-COUCHDB-1852.patch
> When using the EventSource _changes feed support, the browser API will automatically
reconnect and send the last sequence it received in the Last-Event-ID header.
> The server side needs to use the Last-Event-ID instead of the 'since' query string as
a starting point for the changes feed.
> You can see the issue by simply creating a database and adding documents and watching
what happens to the eventsource _changes feed.
> To see the feed with curl use:
> {{curl -i -H 'Last-Event-ID: 2' 'http://localhost:5984/testdb/_changes?feed=eventsource'}}
> the header should also have priority over the since query string:
> {{curl -i -H 'Last-Event-ID: 2' 'http://localhost:5984/testdb/_changes?feed=eventsource?since=1'}}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message