[
https://issues.apache.org/jira/browse/COUCHDB-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422100#comment-15422100
]
Alexander Shorin commented on COUCHDB-3105:
-------------------------------------------
But HTTP defines headers as
[case-insensitive|https://tools.ietf.org/html/rfc7230#section-3.2] entities.
Why Etag name should cause any issues?
> 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
> Affects Versions: 1.6.1
> Reporter: Filippo Fadda
> Priority: Minor
>
> 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)
