[
https://issues.apache.org/jira/browse/COUCHDB-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979563#comment-14979563
]
ASF GitHub Bot commented on COUCHDB-2858:
-----------------------------------------
GitHub user kxepal opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/89
Fix Last-Event-ID header handling for db changes feed
This assumes Last-Event-ID header value to be opaque.
COUCHDB-2858
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kxepal/couchdb-chttpd
2858-fix-last-event-id-header
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/89.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #89
----
commit f071e92a2007c42c74e3455b3b91b37d6185d663
Author: Alexander Shorin <[email protected]>
Date: 2015-10-29T00:38:52Z
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)
