[
https://issues.apache.org/jira/browse/OLINGO-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Reddy resolved OLINGO-846.
---------------------------------
Resolution: Fixed
Assignee: Ramesh Reddy (was: Christian Amend)
Fix Version/s: (Java) V4 4.4.0
Moved the trim after the decoding of the query option string. Also applied same
trim rules to the left of the "=" sign to be more flexible.
> Flexible URL parsing for System Query Options
> ---------------------------------------------
>
> Key: OLINGO-846
> URL: https://issues.apache.org/jira/browse/OLINGO-846
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0-beta-01
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.4.0
>
>
> Salesforce application is generating a OData URL with leading space for
> "$filter" option like
> http://host:port/schema/Entity?$filter= indexof(X, 'x') ne -1
>
> see the leading space before "indexof"? Is this legal URL? Olingo parser
> fails currently with malformed URL error.
> The community discussion is here [1], I am requesting same relaxation of
> rules in parsing in Olingo framework as in .Net framework from Microsoft
> [1]
> http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.apache.olingo.dev+page:1+mid:7rojwqbwjpcsvffw+state:results
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
