Re: Client Explicitly Requesting an Empty Body

• From: Martin Thomson <martin.thomson@gmail.com>
• Date: Wed, 24 Jun 2015 10:39:01 -0700
• To: Brad Fults <bfults@gmail.com>
• Cc: HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <CABkgnnV62v2Gfe9COsnq+Cumq=yVd_B2rV-9JMymP-AWG58=UQ@mail.gmail.com>

Try https://tools.ietf.org/html/rfc7240#section-4.2

On 24 June 2015 at 09:57, Brad Fults <bfults@gmail.com> wrote:
> Hi,
>
> Is there a mechanism for an HTTP client to request that the server
> return an empty body after performing a requested operation? I
> searched specs & mailing list archives to no avail.
>
> For instance, a PATCH on /resource/:id where the client only cares
> that the operation succeeded, but explicitly does not want the
> resource representation returned in the response body (e.g. because it
> will be a large response body and the client is on a limited-bandwidth
> connection). I would expect such a response to return a 204 No Content
> status.
>
> If there is no such current mechanism, would one be considered? One
> possibility would be an `Accept: none` header from the client.
>
> Thanks.
>

Received on Wednesday, 24 June 2015 17:39:29 UTC