curl-library
Re: Ranged PUTs, Content-Range, and Content-Length
Date: Tue, 30 Apr 2019 10:50:53 -0400 (EDT)
On Tue, 30 Apr 2019, Daniel Stenberg wrote:
> RFC 2616 is obsoleted by RFC 7231 and its section 4.3.4 which says:
>
> 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]).
>
> https://tools.ietf.org/html/rfc7231#section-4.3.4
True but organizations that publish stable, long-lived APIs don't
switch from 2616 to 7231 overnight.
m
-- Monty Brandenberg, Software Engineer MCB, Inc. mcbinc_at_panix.com P.O. Box 425292 mcbinc_at_pobox.com Cambridge, MA 02142-0006 617.864.6907 ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2019-04-30