<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
On May 11, 2015, at 1:05 PM, Dean Troyer <<a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a>> wrote:<br>
<div><br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services)
<span dir="ltr"><<a href="mailto:andrea.rosa@hp.com" target="_blank">andrea.rosa@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">
<span class="">> Agreed. Violating the HTTP spec is something that should be avoided.<br>
<br>
</span>Actually it is not violating the HTTP spec, from RFC:<br>
" A payload within a DELETE request message has no defined semantics;<br>
sending a payload body on a DELETE request might cause some existing<br>
implementations to reject the request."<br>
<br>
The RFC prohibit the use of a body just for the TRACE:<br>
" A client MUST NOT send a message body in a TRACE request."<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>When playing in undefined areas such as this it is best to keep in ming Jon Postel's RFC 1122 principle: <span style="font-size: 1em;">"Be liberal in what you accept, and </span><span style="font-size: 1em;">conservative in what you send".</span></div>
<div><span style="font-size: 1em;"><br>
</span></div>
<div><span style="font-size: 1em;">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.</span></div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I’m agreed that this is not a good idea. I’d also invoke the principle of least astonishment here. Because it’s a de facto standard (so much so that some proxy in the middle may alter or reject such a request), it would be surprising to developers to allow
such requests.</div>
<div><br>
</div>
<div>REST APIs are difficult enough. Let’s avoid things with "no defined semantics". </div>
<div><br>
</div>
<div>I’d comment on the review but Gerrit is having a fit so I filed a bug.</div>
<div><br>
</div>
<div><a href="https://code.google.com/p/gerrit/issues/detail?id=3361">https://code.google.com/p/gerrit/issues/detail?id=3361</a></div>
<div><br>
</div>
<div>Everett</div>
<div><br>
</div>
</div>
</body>
</html>