[
https://issues.apache.org/jira/browse/COUCHDB-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011734#comment-14011734
]
ASF subversion and git services commented on COUCHDB-1852:
----------------------------------------------------------
Commit be1643b43106e30ae17e7aac92680c57be7018de in couchdb-chttpd's branch
refs/heads/1843-feature-bigcouch-clustered-eventsource-changes-feed from
[~gdamjan]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=be1643b ]
Support Last-Event-ID header for eventsource changes feeds
COUCHDB-1852
> Last-Event-ID header should be honoured in eventsource _changes feed
> --------------------------------------------------------------------
>
> Key: COUCHDB-1852
> URL: https://issues.apache.org/jira/browse/COUCHDB-1852
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Damjan Georgievski
> Fix For: 1.4.0
>
> Attachments: 0001-add-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 was sent by Atlassian JIRA
(v6.2#6252)
