[
https://issues.apache.org/jira/browse/OLINGO-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856293#comment-15856293
]
Ramesh Reddy commented on OLINGO-1076:
--------------------------------------
I am not say even two is [possibly] wrong, one need to check the HTTP spec as
to what it says as to how one should interpret & followed by a space. No plans
yet on 4.01.
On "skipp" I am saying, there is no such rule that service can not have a valid
parameter with "skipp", so those will not be flagged.
> 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)
