[COUCHDB-13] ETags in response headers do not follow the spec

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.7.2
• Fix Version/s: 0.8
• Component/s: HTTP Interface
• Assignee: Unassigned
• Reporter: Naomi Slater
• Created: 08/Mar/08 23:52
• Updated: 21/Feb/12 22:26
• Resolved: 15/Apr/08 20:09

Description

What steps will reproduce the problem?
1. Request a document
2. See for yourself

What is the expected output? What do you see instead?
Expected is
a) that the header name is "ETag", not "Etag"
b) that the value is a quoted string
Incorrect actual value example:
Etag: 2184611109
Correct expected value example:
ETag: 2184611109

What version of the product are you using? On what operating system?
trunk r591, Mac OS X 10.5.0

Please provide any additional information below.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.11

–

Comment 1 by dzuelke, Nov 16, 2007

Bah, of course the expected value is
ETag: "2184611109"
with quotes.

–

Comment 2 by nslater, Nov 17, 2007

Note: The case of a HTTP header is not important.

It can be "etag", "Etag", "ETag", "eTag", "etAg" or any other combination.

The only thing that needs to change here are the quotes.

–

Comment 3 by dzuelke, Nov 17, 2007

Granted, header field names are case insensitive, but I guess it cannot hurt to stick to the spec, which uses
"ETag"

–

Comment 4 by [e-mail], Jan 26, 2008

A fix relative to rev 640 is attached.