[OASIS Issue Tracker] (ODATA-1025) Treatment of same query option in multiple "spellings"

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64922#comment-64922 ] 

Michael Pizzo commented on ODATA-1025:
--------------------------------------

We actually have this situation already, as HTTP does not prohibit specifying the same query string option more than once; i.e., the client could say $top=5&$top=10.

We currently say, in [Section 5.1, System Query Options](*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#_Toc453752357), of URL Conventions  "The same system query option MUST NOT be specified more than once for any resource."

I would suggest we simply make this rule irrespective of casing or whether it is prefixed with "$".

> Treatment of same query option in multiple "spellings"
> ------------------------------------------------------
>
>                 Key: ODATA-1025
>                 URL: https://issues.oasis-open.org/browse/ODATA-1025
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData URL Conventions
>    Affects Versions: V4.01_CSD01
>            Reporter: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> V4.01 allows to omit the $ prefix for system query options and makes the query option name case-insensitive.
> How should servers react if a request contains e.g. $top=5&Top=10
> Should the request be rejected as the same (logical) query option appears twice, or should it succeed and $top is preferred over Top?
> What if it contains top=5&TOP=10?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)