[
https://issues.apache.org/jira/browse/OLINGO-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579330#comment-17579330
]
mibo commented on OLINGO-1574:
------------------------------
Hi [~varun_ramesh], Thanks for the contribution.
I will check it (which take a bit of time) to see if with this change brings
some [improper error
handling|https://owasp.org/www-community/Improper_Error_Handling] in the way
that it sends detailed internal error messages to the client (reveal
implementation details that should never be revealed).
Kind Regards, Michael
> ODataClientErrorException & ODataServerErrorException doesn't have the
> response body
> ------------------------------------------------------------------------------------
>
> Key: OLINGO-1574
> URL: https://issues.apache.org/jira/browse/OLINGO-1574
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-client
> Affects Versions: (Java) V4 4.9.0
> Reporter: varun_ramesh
> Assignee: mibo
> Priority: Major
> Attachments:
> 0001-OLINGO-1574-enhancement-for-getting-response-in-case.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a OData backend service throws >= 400 error code
> ODataClientErrorException is constructed or if the service throws >= 500 HTTP
> status code Olingo constructs an ODataServerErrorException.
> This exception class doesn't hold the actual response returned by the backend
> system. There are cases where the response from the backend system will be
> useful to determine the actual problem which caused failure HTTP status code.
>
> Hence enhancements should be made to the exception class in a way to retrieve
> the actual response of the backend service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
