You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Michael Bolz (JIRA)" <ji...@apache.org> on 2016/08/30 19:01:20 UTC

[jira] [Resolved] (OLINGO-1016) Wrong batch content header handling (Olingo V2)

     [ https://issues.apache.org/jira/browse/OLINGO-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bolz resolved OLINGO-1016.
----------------------------------
    Resolution: Fixed

Fixed with [this commit|https://git1-us-west.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=0689384db6f11f888faf09d150adb60e654eb6e4].

> Wrong batch content header handling (Olingo V2)
> -----------------------------------------------
>
>                 Key: OLINGO-1016
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1016
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 2.0.7
>            Reporter: Michael Bolz
>            Assignee: Michael Bolz
>             Fix For: V2 2.0.8
>
>
> The parsing of the header in the batch content (in {{BatchParserCommon}}) is not correct.
> Current regex {code}([a-zA-Z\-]+):\s?(.*)\s*{code} does not fit the allowed RFC 7230 HTTP header names consist of the following characters:
> {code}
>        "!" / "#" / "$" / "%" / "&" / "'" / "*"
>      / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
>      / DIGIT / ALPHA
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)