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

Posted to dev@olingo.apache.org by "Shiva Saxena (JIRA)" <ji...@apache.org> on 2018/08/08 17:25:00 UTC

[jira] [Created] (OLINGO-1285) JPA processor returning wrong HTTP status code for DELETE

Shiva Saxena created OLINGO-1285:
------------------------------------

             Summary: JPA processor returning wrong HTTP status code for DELETE
                 Key: OLINGO-1285
                 URL: https://issues.apache.org/jira/browse/OLINGO-1285
             Project: Olingo
          Issue Type: Bug
          Components: odata2-jpa
    Affects Versions: V2 2.0.10
            Reporter: Shiva Saxena


In the function  _build(final DeleteUriInfo deleteUriInfo, final Object deletedObject)_ of class _org.apache.olingo.odata2.jpa.processor.core.ODataJPAResponseBuilderDefault_  the response code 204 being returned.

According to the OData 2 specification status code 200 should be returned.

Quote from the specification.

"Entries are deleted by executing an HTTP DELETE request against a URI that points at the Entry. If the operation executed successfully servers should return 200 (OK) with no response body."

If the status code is not returned properly OData clients that strictly follow the OData specification, might behave unexpectedly, as after firing a DELETE request they will be expecting 200 response, and will get a 204 response.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)