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/29 08:02:21 UTC

[jira] [Resolved] (OLINGO-1015) Wrong batch content header handling

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

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

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

> Wrong batch content header handling
> -----------------------------------
>
>                 Key: OLINGO-1015
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1015
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.2.0
>            Reporter: Michael Bolz
>            Assignee: Michael Bolz
>             Fix For: (Java) V4 4.3.0
>
>
> 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)