You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Alexander Shorin (JIRA)" <ji...@apache.org> on 2015/10/29 15:33:27 UTC
[jira] [Resolved] (COUCHDB-2858) Last-Event-ID not working on
cluster
[ https://issues.apache.org/jira/browse/COUCHDB-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Shorin resolved COUCHDB-2858.
---------------------------------------
Resolution: Fixed
> Last-Event-ID not working on cluster
> ------------------------------------
>
> Key: COUCHDB-2858
> URL: https://issues.apache.org/jira/browse/COUCHDB-2858
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Sebastian Rothbucher
> Assignee: Alexander Shorin
> Priority: Blocker
> Fix For: 2.0.0
>
>
> req = CouchDB.request("GET", "/" + db_name + "/_changes?feed=eventsource&timeout=0&since=0",
> - {"headers": {"Accept": "text/event-stream", "Last-Event-ID": "2"}}); + {"headers": {"Accept": "text/event-stream", "Last-Event-ID": JSON.stringify(JSON.parse(req.responseText).results[1].seq)}});
> filling Last-Event-ID with a "complex" Seq yields an error
> from changes.js test case
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)