[jira] [Updated] (OLINGO-846) Flexible URL parsing for System Query Options

["Michael Bolz (JIRA)" <ji...@apache.org>]

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

Michael Bolz updated OLINGO-846:
--------------------------------
    Fix Version/s:     (was: (Java) V4 4.2.0)

> 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: Christian Amend
>
> 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.4#6332)