[
https://issues.apache.org/jira/browse/OLINGO-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275328#comment-15275328
]
Peter Rilling commented on OLINGO-945:
--------------------------------------
Perhaps,
It took a whole day to discover this (debugging into OLingo code) because it's
not obvious and the OData examples use only one blank line.
http://www.odata.org/documentation/odata-version-2-0/batch-processing/
That and also some clients may only place one line, making usage impossible.
Also, I may not know the intricacies of the various specs', but I don't think
your first two CRLF items above are mutually exclusive. If you have ONE blank
line, that would satisfy both requirements.
> Single blank line at end of batch part causes error.
> ----------------------------------------------------
>
> Key: OLINGO-945
> URL: https://issues.apache.org/jira/browse/OLINGO-945
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.6
> Reporter: Peter Rilling
>
> When constructing batch requests, if there is less than two blank lines
> before the closing batch part marker, you get the error "Expected empty line
> but was '[None]'".
> For example, the following works:
> {code}--batch_36522ad7-fc75-4b56-8c71-56071383e77b
> Content-Type: application/http
> GET Pages HTTP/1.1
> --batch_36522ad7-fc75-4b56-8c71-56071383e77b--{code}
> But the following does not:
> {code}--batch_36522ad7-fc75-4b56-8c71-56071383e77b
> Content-Type: application/http
> GET Pages HTTP/1.1
> --batch_36522ad7-fc75-4b56-8c71-56071383e77b--{code}
> Notice how the only difference is the number of lines after the GET.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
