couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Lenz (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-13) ETags in response headers do not follow the spec
Date Mon, 24 Mar 2008 22:47:26 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher Lenz updated COUCHDB-13:
------------------------------------

    Component/s: HTTP Interface

> ETags in response headers do not follow the spec
> ------------------------------------------------
>
>                 Key: COUCHDB-13
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-13
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>            Reporter: Noah Slater
>            Priority: Minor
>         Attachments: couchdb.patch
>
>
> 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 aristid....@gmx.de, Jan 26, 2008
> A fix relative to rev 640 is attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message