You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@couchdb.apache.org by Michael Hendricks <mi...@ndrix.org> on 2008/11/01 17:19:57 UTC

status code for invalid database names

Currently, CouchDB returns a 500 status code when trying to create a
database with an invalid name (like "12345").  Shouldn't that be a 400
status code ("Bad Request") since the error really lies with the
client and not the server?

If others agree, I'll submit a patch.

-- 
Michael

Re: status code for invalid database names

Posted by Chris Anderson <jc...@apache.org>.

On Sat, Nov 1, 2008 at 9:43 AM, Noah Slater <ns...@apache.org> wrote:
> On Sat, Nov 01, 2008 at 10:19:57AM -0600, Michael Hendricks wrote:
>> Currently, CouchDB returns a 500 status code when trying to create a
>> database with an invalid name (like "12345").  Shouldn't that be a 400
>> status code ("Bad Request") since the error really lies with the
>> client and not the server?
>>
>> If others agree, I'll submit a patch.
>
> +1
>

+1 thanks


-- 
Chris Anderson
http://jchris.mfdz.com

Re: status code for invalid database names

Posted by Noah Slater <ns...@apache.org>.

On Sat, Nov 01, 2008 at 10:19:57AM -0600, Michael Hendricks wrote:
> Currently, CouchDB returns a 500 status code when trying to create a
> database with an invalid name (like "12345").  Shouldn't that be a 400
> status code ("Bad Request") since the error really lies with the
> client and not the server?
>
> If others agree, I'll submit a patch.

+1

-- 
Noah Slater, http://bytesexual.org/nslater