Hi Ramesh, based on my reading of the ABNF I don’t think that URL is technically legal, but in our .NET libraries we have a principle of "lenient on read, strict on write". This seems like a case where the intention of the URL is pretty clear and so in our .NET libraries if we were dealing with this particular issue, we would parse the URL without an error. We would, however, never send a response that contains an invalid URL.
-----Original Message----- From: Ramesh Reddy [mailto:[email protected]] Sent: Wednesday, January 6, 2016 4:21 AM To: [email protected] Subject: Leading space in the OData URL System Query Options Hi, One of our community member is faced with a issue [1], where a 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. Thanks Ramesh.. https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fteiid.org&data=01%7c01%7cmastaffo%40microsoft.com%7ccef42bf6f20d45f2008208d3160dd212%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=uBrmChzYVO43G8VEu007iNB4yHAJdpm7LHyCmg6CpeU%3d [1] https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdeveloper.jboss.org%2fmessage%2f948398&data=01%7c01%7cmastaffo%40microsoft.com%7ccef42bf6f20d45f2008208d3160dd212%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=tp%2bPtHCURRMQd3xP%2fsUhqbPT0ob8jtoNFEO4bkE7SMw%3d
