Hi, Jay, an explanation would be appreciated as it seems 409 doesn't match HTTP RFC[1] [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html Cédric/ZZelle On Fri, Feb 26, 2016 at 4:36 PM, Jay Pipes <jaypipes at gmail.com> wrote: > On 02/26/2016 09:02 AM, Akihiro Motoki wrote: > >> Hi API-WG, >> >> Neutron is implementing tag support for network resource [0]. >> The implementation follows 'Tags' guideline defined by API-WG [1]. >> I have a questions on the guideline. >> >> ---- >> >> We can create a tag by PUT'ing an individual tag: >> What status code should be returned if a requested tag already exists? >> >> PUT /servers/1234567890/tags/qux >> >> The guideline defines 201 (+ Location header) on success. >> In the current neutron implementation proposed, 409 is returned >> when a requested tag already exists. >> > > 409 Conflict. > > Best, > -jay > > > __________________________________________________________________________ > 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/20160226/75c8b899/attachment.html>