You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by "Filippo Fadda (JIRA)" <ji...@apache.org> on 2016/08/15 20:39:20 UTC

[jira] [Created] (COUCHDB-3105) Etag must be renamed to ETag

Filippo Fadda created COUCHDB-3105:
--------------------------------------

             Summary: Etag must be renamed to ETag
                 Key: COUCHDB-3105
                 URL: https://issues.apache.org/jira/browse/COUCHDB-3105
             Project: CouchDB
          Issue Type: Bug
          Components: HTTP Interface
            Reporter: Filippo Fadda


According to HTTP protocol documentation, an entity-tag can be either a weak or strong validator, with strong being the default. If an origin server provides an entity-tag for a representation and the generation of that entity-tag does not satisfy all of the characteristics of a strong validator (Section 2.1), then
the origin server MUST mark the entity-tag as weak by prefixing its
opaque value with "W/" (case-sensitive).

Actually CouchDB returns Etag instead of ETag. This is a wrong behaviour and it forces to use a weak validator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)