[
https://issues.apache.org/jira/browse/OLINGO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541210#comment-16541210
]
Aarzoo Aggarwal commented on OLINGO-1274:
-----------------------------------------
I am rephrasing this whole conversation for confirmation.Please correct me if I
am wrong somewhere.
1) You will be changing the OData specification to reflect the meaning
/interpretation clearly but there is no change /fix expected for this "code" to
be reflected in response body ?
2) Also , the Odata clients don't expect this to be a compulsory field and any
client should be able to correctly accept the response even with this field as
null in body.
> URIParserError gives null response code in response body
> --------------------------------------------------------
>
> Key: OLINGO-1274
> URL: https://issues.apache.org/jira/browse/OLINGO-1274
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core, odata4-client, odata4-commons, odata4-server
> Affects Versions: (Java) V4 4.4.0
> Reporter: Aarzoo Aggarwal
> Priority: Blocker
>
> We create an entity query relation like below -
> The request -
> [http://ip:host/odata/entity(x)?$filter=z%20eq%203|http://iphost/]
> Very obviously , we cannot create a filter on a single entity.But the problem
> is that the response that we recieve is as below -
> {
> "error":
> { "code": null, "message": "The system query option '$filter' is not
> allowed." }
> }
>
> We expect a valid status code to be returned here .
> Is any resolution for this issue available ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
