[
https://issues.apache.org/jira/browse/COUCHDB-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714443#comment-13714443
]
ASF subversion and git services commented on COUCHDB-1852:
----------------------------------------------------------
Commit dfd2199a4c6f67b76018eccfdd00b4fd4190e392 in branch refs/heads/master
from [~gdamjan]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=dfd2199 ]
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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
