[jira] [Closed] (COUCHDB-2654) Support Content-Range for Attachment PUT requests

["Robert Newson (JIRA)" <ji...@apache.org>]

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

Robert Newson closed COUCHDB-2654.
----------------------------------
    Resolution: Won't Fix

This has been raised before. Unfortunately the spec has been clarified that this is not permitted;

rfc 7231

An origin server that allows PUT on a given target resource MUST send
   a 400 (Bad Request) response to a PUT request that contains a
   Content-Range header field (Section 4.2 of [RFC7233]), since the
   payload is likely to be partial content that has been mistakenly PUT
   as a full representation.  Partial content updates are possible by
   targeting a separately identified resource with state that overlaps a
   portion of the larger resource, or by using a different method that
   has been specifically defined for partial updates (for example, the
   PATCH method defined in [RFC5789]).

> Support Content-Range for Attachment PUT requests
> -------------------------------------------------
>
>                 Key: COUCHDB-2654
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2654
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Database Core, HTTP Interface
>            Reporter: Matthias Reik
>
> This ticket is a result of my question on [stackoverflow|http://stackoverflow.com/questions/29228210/does-couchdb-suppport-content-range-in-attachment-put-requests]
> It would be nice to add support for updating/editing/adding to an existing attachment by making use of the Content-Range header on PUT requests. It is already supported for GET requests (even though not sure whether it's according to [RFC 2616|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.16])



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)