Bad response status on decribe table with empty name

Bug #1298838 reported by Andrii Ostapenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MagnetoDB
Low
Annapoornima Koppad

Bug Description

2014-03-28 08:00:32,847 Request: GET http://localhost:8480/v1/default_tenant/data/tables/
2014-03-28 08:00:32,848 Request Headers: {'Content-Type': 'application/json', 'Accept': 'application/json'}
2014-03-28 08:00:32,850 Response Status: 404
2014-03-28 08:00:32,850 Response Headers: {'date': 'Fri, 28 Mar 2014 08:00:32 GMT', 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'}
2014-03-28 08:00:32,850 Response Body: 404 Not Found

The resource could not be found.

Expected status: 400

Changed in magnetodb:
status: New → Incomplete
Changed in magnetodb:
importance: Undecided → Low
tags: added: data-api validation
Changed in magnetodb:
milestone: none → 2.0.5
Changed in magnetodb:
milestone: 2.0.5 → next
Changed in magnetodb:
milestone: next → none
Revision history for this message
Rushi Agrawal (rushiagr) wrote :

I'm marking it to 'New' again, as no sufficient reason was provided while marking this 'Incomplete'. This is to ensure that the bug don't get expired

Changed in magnetodb:
status: Incomplete → New
Revision history for this message
Ilya Sviridov (isviridov) wrote : Re: [Bug 1298838] Re: Bad response status on decribe table with empty name

Thank you, Rushi

But 404 looks good here.

The only thing what can be improved is body.
It is default output now, but could be smth meaningful like json
formatted error message.

Ilya

27.11.2014 12:07, Rushi Agrawal пишет:
> I'm marking it to 'New' again, as no sufficient reason was provided
> while marking this 'Incomplete'. This is to ensure that the bug don't
> get expired
>
> ** Changed in: magnetodb
> Status: Incomplete => New
>

Changed in magnetodb:
milestone: none → kilo-1
status: New → Triaged
tags: added: low-hanging-fruit
removed: validation
Revision history for this message
Ilya Sviridov (isviridov) wrote :

Here are some best practices

http://books.google.com.ua/books?id=4lZcsRwXo6MC&printsec=frontcover&hl=ru&source=gbs_ge_summary_r&cad=0#v=onepage&q=Rule%3A%20404&f=false

And in openstack keystone response
http://stack:5000/v2.0/tokens

<error message="The resource could not be found." code="404" title="Not Found"/>

Changed in magnetodb:
milestone: kilo-1 → kilo-2
Changed in magnetodb:
milestone: kilo-2 → kilo-3
Changed in magnetodb:
milestone: kilo-3 → l-1
Changed in magnetodb:
assignee: nobody → pradeep kumar singh (pradeep-singh-u)
Changed in magnetodb:
assignee: pradeep kumar singh (pradeep-singh-u) → nobody
Changed in magnetodb:
assignee: nobody → Annapoornima Koppad (annakoppad)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers