[
https://issues.apache.org/jira/browse/OLINGO-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673218#comment-15673218
]
Frederik Zimmer commented on OLINGO-1046:
-----------------------------------------
But what does "bad" mean? They are part of the ABNF so a filter option with the
BWS is a valid filter option. Maybe they should have called them deprecated.
rfc7230 has a definition of BWS:
"The BWS rule is used where the grammar allows optional whitespace only for
historical reasons. A sender MUST NOT generate BWS in messages. A recipient
MUST parse for such bad whitespace and remove it before interpreting the
protocol element."
So you MUST be able to parse them to be spec conform.
> Whitespaces in functions not allowed
> ------------------------------------
>
> Key: OLINGO-1046
> URL: https://issues.apache.org/jira/browse/OLINGO-1046
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.3.0
> Reporter: Frederik Zimmer
>
> Whitespaces before/after comma/parenthesis in functions are allowed by the
> ABNF but Olingo is unable to parse them.
> This would result in an error (inserted space after comma in Testcase of
> TestFullResourcePath):
> startswith(PropertyCompAllPrim/PropertyString, 'Wall')
> ABNF example:
> startsWithMethodCallExpr = 'startswith' OPEN BWS commonExpr BWS COMMA BWS
> commonExpr BWS CLOSE
> BWS = *( SP / HTAB / "%20" / "%09" ) ; "bad" whitespace
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
