[
https://issues.apache.org/jira/browse/COUCHDB-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980516#comment-14980516
]
ASF subversion and git services commented on COUCHDB-2858:
----------------------------------------------------------
Commit 2147dba9c87ae0ae39206009bdb2784108507a16 in couchdb-chttpd's branch
refs/heads/master from [~kxepal]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=2147dba ]
Fix Last-Event-ID header handling for db changes feed
This assumes Last-Event-ID header value to be opaque.
COUCHDB-2858
> Last-Event-ID not working on cluster
> ------------------------------------
>
> Key: COUCHDB-2858
> URL: https://issues.apache.org/jira/browse/COUCHDB-2858
> Project: CouchDB
> Issue Type: Bug
> 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)
