[
https://issues.apache.org/jira/browse/OLINGO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538722#comment-16538722
]
Ramesh Reddy commented on OLINGO-1274:
--------------------------------------
Here is the relevant verbiage from OData spec
[http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#_Toc505771158]
It does not call out for 400 code but could be interpreted as such. The TripPin
service on Odata.org also does error response like
{"error":\{"code":"","message":"The request resource is not found."}}
[~RalfHandl] what do you suggest?
> 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)
