Bug #669
Dryad MN not returning 404 correctly
100%
Description
Issuing a get() against a non-existent resource returns an error document bu the status code of the response is still 200.
The HTTP status code returned in the header and the errorCode in the document should match.
History
#1 Updated by Roger Dahl almost 14 years ago
- Status changed from New to Closed
#2 Updated by Dave Vieglais almost 14 years ago
- Status changed from Closed to 4
Re-opening this because the problem still exists. HTTP Status being returned for a non-existent object is 200 rather than the expected 404. For example:
curl -v dev-dryad-mn.dataone.org/mn/object/bogus
* About to connect() to dev-dryad-mn.dataone.org port 80 (#0)
* Trying 129.24.0.11... connected
* Connected to dev-dryad-mn.dataone.org (129.24.0.11) port 80 (#0)
GET /mn/object/bogus HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Host: dev-dryad-mn.dataone.org
Accept: /< HTTP/1.1 200 OK
< Date: Wed, 23 Jun 2010 13:46:44 GMT
< Server: Apache/2.2.14 (Ubuntu)
< Vary: Cookie
< Transfer-Encoding: chunked
< Content-Type: 404
<
Non-existing scimeta object was requested: bogus'mn_prototype.mn_service.views'
#3 Updated by Roger Dahl over 13 years ago
- Status changed from 4 to Closed
I think I had not pushed the change out when you tested. It works now.
#4 Updated by Dave Vieglais over 11 years ago
- Start date set to 2013-01-02
- translation missing: en.field_remaining_hours set to 0.0
- Category changed from 299 to mn.Dryad
- Due date set to 2013-01-02
