[
https://issues.apache.org/jira/browse/COUCHDB-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850673#action_12850673
]
Robert Newson commented on COUCHDB-711:
---------------------------------------
RFC 2616 is the authority on this;
9.6
PUT "Responses to this method are not cacheable."
10.2.2 201 Created
A 201 response MAY contain an ETag response header field indicating the current
value of the entity tag for the requested variant just created, see section
14.19.
-------------
So I think we should add ETag to all PUT/DELETE responses, but that doesn't
imply that the response body is cacheable.
> missing etag header when putting standalone attachments
> -------------------------------------------------------
>
> Key: COUCHDB-711
> URL: https://issues.apache.org/jira/browse/COUCHDB-711
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 0.10.1
> Reporter: Niko Uphoff
> Attachments: attachments_etags.patch, etag_for_standalone_put.diff
>
>
> when putting standalone attachments there is no etag header in the response
> _________________________________________________________________
> curl -X PUT -i http://127.0.0.1:5984/test/test/attachment \
> -H 'Content-Type: text/plain' \
> --data 'some text'
> will just return
> HTTP/1.1 201 Created
> Server: CouchDB/0.10.1 (Erlang OTP/R13B)
> Location: http://127.0.0.1:5984/test/test/attachment
> Date: Fri, 26 Mar 2010 14:17:39 GMT
> Content-Type: text/plain;charset=utf-8
> Content-Length: 67
> Cache-Control: must-revalidate
> {"ok":true,"id":"test","rev":"1-3fed07956fe933df5a6dd8dd05a73ca7"}
> _________________________________________________________________
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
