Open Stack

Can you give an example of an Object HEAD request returning 204?  I tried a
HEAD of an object with a body and also a HEAD of an object of length 0 and
I seem to get 200's...

Container's and accounts are a little more interesting story... [2]

-Clay

2. https://review.openstack.org/#/c/32647/

On Wed, May 6, 2015 at 5:40 PM, Ouchi, Atsuo <ouchi.atsuo at jp.fujitsu.com>
wrote:

> Hello Swift developers,
>
> I would like to ask you on a Swift API specification.
>
> Swift returns 204 status code to a valid HEAD Object request with a
> Content-Length header,
> whereas the latest HTTP/1.1 specification (RFC7230) states that you must
> not send
> the header with a 204 status code.
>
> > 3.3.2.  Content-Length
> (snip)
> >    A server MUST NOT send a Content-Length header field in any response
> >    with a status code of 1xx (Informational) or 204 (No Content).  A
> >    server MUST NOT send a Content-Length header field in any 2xx
> >    (Successful) response to a CONNECT request (Section 4.3.6 of
> >    [RFC7231]).
>
> What I would like to know is, when you designed Swift APIs what was the
> reasoning
> behind choosing 204 status code to HEAD Object, over other status codes
> such as 200?
>
> Thanks,
> Atsuo
> --
>                                        Ouchi Atsuo /
> ouchi.atsuo at jp.fujitsu.com
>                                            tel. 03-6424-6612 / ext.
> 72-60728968
>                     Service Development Department, Foundation Service
> Division
>                                                                 Fujitsu
> Limited
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150506/96b98e5a/attachment.html>