[
https://issues.apache.org/jira/browse/COUCHDB-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236814#comment-15236814
]
ASF subversion and git services commented on COUCHDB-2978:
----------------------------------------------------------
Commit 301570f741e4e1c19c0d939b054e64c0ef407ce0 in couchdb's branch
refs/heads/update-rebar from [~garren]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=301570f ]
Update rebar for COUCHDB-2978
Update rebar and couch for latest changes to chttpd and couch.
> Stale ETags are re-used for _local docs
> ---------------------------------------
>
> Key: COUCHDB-2978
> URL: https://issues.apache.org/jira/browse/COUCHDB-2978
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Nolan Lawson
> Priority: Blocker
> Fix For: 1.7.0
>
>
> CouchDB re-uses the same ETags for _local documents even when the content of
> the _local document has changed, meaning that clients who cache based on the
> ETag may end up with permanently stale content. To reproduce the bug, it's
> simply:
> 1. Create a _local doc
> 2. Fetch the doc, ETag is "0-1"
> 3. Delete the database (or the _local doc)
> 4. Recreate the database (or the _local doc), insert a *changed* _local doc
> 5. Fetch the doc, ETag is still "0-1" and therefore the client may end up
> with a stale version.
> Here are related issues in PouchDB and WebKit for further details:
> - [PouchDB bug|https://github.com/pouchdb/pouchdb/issues/5010]
> - [WebKit bug|https://bugs.webkit.org/show_bug.cgi?id=156048]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
