On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services) < andrea.r...@hp.com> wrote:
> > Agreed. Violating the HTTP spec is something that should be avoided. > > Actually it is not violating the HTTP spec, from RFC: > " A payload within a DELETE request message has no defined semantics; > sending a payload body on a DELETE request might cause some existing > implementations to reject the request." > > The RFC prohibit the use of a body just for the TRACE: > " A client MUST NOT send a message body in a TRACE request." > When playing in undefined areas such as this it is best to keep in ming Jon Postel's RFC 1122 principle: "Be liberal in what you accept, and conservative in what you send". I'll put it this way: An RFC not prohibiting something does not make it a good idea. This is not how we build a robust API that developers and user can easily adopt. dt Dean Troyer dtro...@gmail.com
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
