Thanks for addressing this bug, Justin. I'm not so sure I agree with this behavior. If you try to POST with an image id that is already taken, the client should get a 400 Bad Request. It seems counterintuitive to me to effectively do a PUT and update an existing image when the creation of a new image was expected. What do you think?
Thanks for addressing this bug, Justin. I'm not so sure I agree with this behavior. If you try to POST with an image id that is already taken, the client should get a 400 Bad Request. It seems counterintuitive to me to effectively do a PUT and update an existing image when the creation of a new image was expected. What do you think?