Bug 1316500 - OData - Request entity which does not exist return 204 instead of 404
Summary: OData - Request entity which does not exist return 204 instead of 404
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER2
: 6.3.0
Assignee: Van Halbert
QA Contact: Juraj Duráni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 11:16 UTC by Juraj Duráni
Modified: 2016-08-24 11:39 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:39:13 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4058 0 Major Resolved OData - Request entity which does not exist return 204 instead of 404 2016-05-25 13:18:03 UTC

Description Juraj Duráni 2016-03-10 11:16:51 UTC 
Description of problem:
If entity with requested ID does not exist, OData service should return 404 but Teiid returns 204.

*URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView(-2)

Moreover, if users define also property in the URL, Teiid returns 404, but body is neither in XML nor in JSON format (seems like generic EAP error page).

*URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView(-2)/intkey

See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398293
Comment 1 JBoss JIRA Server 2016-03-11 14:04:20 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-4058 to Resolved
Comment 2 Juraj Duráni 2016-05-25 13:20:47 UTC 
Teiid returns 404 if entity does not exist. Verified.

Regarding generic EAP error page - this is separate issue.
Note You need to log in before you can comment on or make changes to this bug.