+1 on this sentiment.
From the perspective of the client, I typically imagine a web browser. A 404
means that a thing was not found and this **implies** that I might specify a
different thing so that I do *not* get a 404. But in many of the
circumstances the 404 root cause is a server-side
On Tue, Nov 26, 2013 at 7:27 AM, Matt Riedemann
mrie...@linux.vnet.ibm.comwrote:
Aaron Rosen is working a patch [1] to handle a NetworkNotFound exception
in the server create API. For the V2 API this will return a 400 error.
For the V3 API this will return a 404 because of a V3-specific
On Mon, Nov 25, 2013 at 6:00 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Tue, Nov 26, 2013 at 7:27 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
Aaron Rosen is working a patch [1] to handle a NetworkNotFound exception
in the server create API. For the V2 API this will return a
On Tue, Nov 26, 2013 at 9:41 AM, Aaron Rosen aaronoro...@gmail.com wrote:
On Mon, Nov 25, 2013 at 6:00 PM, Christopher Yeoh cbky...@gmail.comwrote:
On Tue, Nov 26, 2013 at 7:27 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
Aaron Rosen is working a patch [1] to handle a
