[
https://issues.apache.org/jira/browse/OLINGO-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-494.
------------------------------------
Resolution: Fixed
Fix Version/s: V2 2.0.2
Hi,
this issue was fixed with the following commit:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=297c3949222e50de4a6c266e4a221564ad2d9b08
Best Regards,
Christian
> Content-Length HTTP Header is missing when using ODataServlet
> -------------------------------------------------------------
>
> Key: OLINGO-494
> URL: https://issues.apache.org/jira/browse/OLINGO-494
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-core
> Affects Versions: V2 2.0.1
> Reporter: Vitali Yarmolik
> Assignee: Christian Amend
> Fix For: V2 2.0.2
>
>
> {{Content-Length}} HTTP Header is missing in the responses of the OData
> service when using {{ODataServlet}} in web.xml. The header is added when
> {{CXFNonSpringJaxrsServlet}} is used.
> I'm not sure whether it's mandatory, because I haven't found any requirements
> in the OData specification. Nevertheless, the service behavior is different
> depending on what servlet is used in web.xml. Probably this difference should
> be mentioned in the library documentation.
> In my particular case, the absence of the {{Content-Length}} HTTP Header
> caused failure of some of the service-related tests. I think that there is a
> probability that it can cause some issues in the service-based client
> applications as well after switching to {{ODataServlet}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
