[jira] [Commented] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces

2017-03-25 Thread Michael Bolz (JIRA)

[ 
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941631#comment-15941631
 ] 

Michael Bolz commented on OLINGO-1097:
--

Hi [~dtretyakov],

Thanks for the contribution.
I fixed a minor checkstyle issue and pushed it with [this 
commit|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=cceffb31024be8e94a210c344ee68b6b98ddfdfb].

Best Regards, Michael

> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
>  Issue Type: Bug
>  Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Michael Bolz
>  Labels: patch
> Fix For: V2 2.0.9
>
> Attachments: 
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field 
> values with comma and only one white space it causes that after parsing 
> values are prefixed by white spaces which causes exceptions in `ContentType` 
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2: 
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml,  application/xml
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces

2017-03-24 Thread Christian Amend (JIRA)

[ 
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940102#comment-15940102
 ] 

Christian Amend commented on OLINGO-1097:
-

Will take a look this weekend.

> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
>  Issue Type: Bug
>  Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Christian Amend
>  Labels: patch
> Fix For: V2 2.0.9
>
> Attachments: 
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field 
> values with comma and only one white space it causes that after parsing 
> values are prefixed by white spaces which causes exceptions in `ContentType` 
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2: 
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml,  application/xml
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces

2017-03-22 Thread Dmitry Tretyakov (JIRA)

[ 
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936304#comment-15936304
 ] 

Dmitry Tretyakov commented on OLINGO-1097:
--

Attaching patch and test

> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
>  Issue Type: Bug
>  Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>  Labels: patch
> Fix For: V2 2.0.9
>
> Attachments: 
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field 
> values with comma and only one white space it causes that after parsing 
> values are prefixed by white spaces which causes exceptions in `ContentType` 
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2: 
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)