[
https://issues.apache.org/jira/browse/OLINGO-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963495#comment-15963495
]
Ramesh Reddy commented on OLINGO-1076:
--------------------------------------
[~nvsreddy] See
http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part2-url-conventions/odata-v4.0-errata03-os-part2-url-conventions-complete.html#_Toc453752335
for URL encoding rules.
As I mentioned before "$top=2 & $skip=19 --> Here skip is ignored (space
between & and $)" is only one to make it more relaxed. There few more
enhancements to make the OData little more flexible in allowing non-strict
OData URL constructs from client perspective. Since they are not bugs I am not
sure the inclination of the project commiters to take upon the task.
> Validating Query Options for correct syntax
> -------------------------------------------
>
> Key: OLINGO-1076
> URL: https://issues.apache.org/jira/browse/OLINGO-1076
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.3.0
> Reporter: VIJAYASIMHA R NAGA
> Priority: Minor
>
> Currently if any query options are used incorrectly, the URL parser ignores
> the same and does not flag any error and the same affects the contents in
> result set, few examples
> ?$top=2 & skipp=19 --> "skip" mis-spelt as "skipp"
> ?$top=2 & $skip=19 --> Here skip is ignored (space between & and $)
> ?filter=Name eq 'XYZ' --> Here filter segment is ignored (missing $)
> Is it possible to add some validation in the URL parser?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
