You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Ramya (JIRA)" <ji...@apache.org> on 2018/04/25 08:51:00 UTC
[jira] [Commented] (OLINGO-1238) OData V4: Code Improvements in
handling exceptions
[ https://issues.apache.org/jira/browse/OLINGO-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451907#comment-16451907 ]
Ramya commented on OLINGO-1238:
-------------------------------
Additional code fixes as part of the comit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=c81833d50e9ab34a8b939584fc04f33eec8ba68b
> 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)