[
https://issues.apache.org/jira/browse/OLINGO-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023196#comment-18023196
]
Pawel Wolanski commented on OLINGO-1644:
----------------------------------------
when all http headers are imported to ODataResponseImpl, are lower-case. Then
contentType attribute is not read from map:
!Screenshot 2025-09-26 at 22.15.03.png!
> olingo v2 ODataResponse is case sensitive for HTTP headers
> ----------------------------------------------------------
>
> Key: OLINGO-1644
> URL: https://issues.apache.org/jira/browse/OLINGO-1644
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.13
> Reporter: Pawel Wolanski
> Priority: Major
> Fix For: V2 2.1.0
>
> Attachments: Screenshot 2025-09-26 at 22.15.03.png
>
>
> current Olingo implementation of 2.0.13 is case sensitive while getting
> essential headers from http header response.
> In our case content-type is not parsed correctly and treated as a null, while
> application add it in the response.
>
> By the HTTP standard description describes HTTP headers are case-insensitive.
> "
> * {*}RFC 2616 (HTTP/1.1){*}, Section 4.2: "Each header field consists of a
> name followed by a colon (':') and the field value. Field names are
> case-insensitive.".
> "
>
> [https://www.w3.org/Protocols/rfc2616/rfc2616.html]
>
> [https://www.rfc-editor.org/rfc/rfc7230#appendix-A.2]
>
> "
> [3.2|https://www.rfc-editor.org/rfc/rfc7230#section-3.2]. Header Fields
> Each header field consists of a case-insensitive field name followed
> by a colon (":"), optional leading whitespace, the field value, and
> optional trailing whitespace.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
