<div dir="ltr"><div><div>Hi,<br><br></div>Jay, an explanation would be appreciated as it seems 409 doesn't match HTTP RFC[1]<br><br><br>[1] <a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html">https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html</a><br><br></div>Cédric/ZZelle<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 26, 2016 at 4:36 PM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 02/26/2016 09:02 AM, Akihiro Motoki wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi API-WG,<br>
<br>
Neutron is implementing tag support for network resource [0].<br>
The implementation follows 'Tags' guideline defined by API-WG [1].<br>
I have a questions on the guideline.<br>
<br>
----<br>
<br>
We can create a tag by PUT'ing an individual tag:<br>
What status code should be returned if a requested tag already exists?<br>
<br>
PUT /servers/1234567890/tags/qux<br>
<br>
The guideline defines 201 (+ Location header) on success.<br>
In the current neutron implementation proposed, 409 is returned<br>
when a requested tag already exists.<br>
</blockquote>
<br></span>
409 Conflict.<br>
<br>
Best,<br>
-jay<div class="HOEnZb"><div class="h5"><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>