You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Vitali Yarmolik (JIRA)" <ji...@apache.org> on 2014/11/21 15:15:34 UTC

[jira] [Created] (OLINGO-494) Content-Length HTTP Header is missing when using ODataServlet

Vitali Yarmolik created OLINGO-494:
--------------------------------------

             Summary: 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


{{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)