olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "VIJAYASIMHA R NAGA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLINGO-1076) Validating Query Options for correct syntax
Date Thu, 09 Feb 2017 01:08:41 GMT

    [ https://issues.apache.org/jira/browse/OLINGO-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858814#comment-15858814

VIJAYASIMHA R NAGA commented on OLINGO-1076:

Hi Ramesh,
are you saying that HTTP Spec allows the service discarding the content that appears after
"&" with a space in between or do we need to take a detailed look at HTTP spec to understand
and what are your thoughts about allowing reserved characters for the value of an Entity key
of type string Ex: "'xyz:1/2')/SampleProperty"
by leveraging the enclosing parenthesis to ignore the "/" within the key and not interpret
it as path segment delimiter ?

> 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

View raw message