[COUCHDB-3105] Etag must be renamed to ETag

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 1.6.1
• Component/s: HTTP Interface
• Assignee: Unassigned
• Reporter: Filippo Fadda
• Created: 15/Aug/16 20:38
• Updated: 02/Sep/16 11:46
• Resolved: 02/Sep/16 11:46

Description

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.