[jira] [Commented] (COUCHDB-2978) Stale ETags are re-used for _local docs

["Jan Lehnardt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219898#comment-15219898 ] 

Jan Lehnardt commented on COUCHDB-2978:
---------------------------------------

Via IRC discussion:

rnewson:	I think the best fix is to not add ETag for _local docs
jan____: 	in this case we should not send an ETag for local docs, and we should whatever no-cache headers that are appropriate

e.g.: this bug is on us.

> 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
>             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)