[
https://issues.apache.org/jira/browse/OLINGO-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801612#comment-16801612
]
Archana Rai commented on OLINGO-1315:
-------------------------------------
The issues are resolved with:
[https://gitbox.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=f91568e1abe6e4b606d541d6c3a85218d6ab739e]
and
[https://gitbox.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=5b32c3acbf026140b39b308d7fc3b56a145f8947].
Hence closing this.
> ODATA V4.0 Client: API to return HTTP Request details
> -----------------------------------------------------
>
> Key: OLINGO-1315
> URL: https://issues.apache.org/jira/browse/OLINGO-1315
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-client
> Reporter: Archana Rai
> Priority: Minor
> Fix For: (Java) V4 4.6.0
>
>
> The library provides the ODataRequest to the application developer. The
> ODataRequest internally uses HttpRequest. Currently, there is no way to get
> hold of the actual HttpRequest which can be helpful for audit and analysis of
> an error scenario. An api getHttpRequest within ODataRequest can be helpful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
