[
https://issues.apache.org/jira/browse/OLINGO-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487022#comment-16487022
]
Ramya commented on OLINGO-1238:
-------------------------------
Get and Delete requests should fail with 400 Bad Request when Prefer header is
set with return=minimal or return=representation.
Any request for stream properties should fail with 400 Bad Request when Prefer
header is set with return=minimal or return=representation.
This is fixed as part of the commit
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=03a02d2d69f2a76aba1db889ca5e94606cd3e7ed
> OData V4: Code Improvements in handling exceptions
> --------------------------------------------------
>
> Key: OLINGO-1238
> URL: https://issues.apache.org/jira/browse/OLINGO-1238
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.4.0
> Reporter: Ramya
> Priority: Major
>
> When the OData-Version header is specified less than 4.0 then we throw 400
> Bad Request error and when the value is greater than 4.01 we throw 400 Bad
> Request error
> When the OData-MaxVersion header is specified less than 4.0 then we throw 400
> Bad Request error and when the value is greater than 4.01 the request is
> processed.
> When the Accept header has a charset which violates ABNF, we throw 400 Bad
> Request and if it is as per ABNF but wrong format like application/abc, then
> we throw 406 Not Acceptable.
> When the Accept charset header has a charset which violates ABNF, we throw
> 400 Bad Request and if it is as per ABNF but other than utf-8, then we throw
> 406 Not Acceptable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
