Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-1541

Forward slashes in /$filter segments

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.01_OS
    • Fix Version/s: V4.01_ERRATA01
    • Component/s: URL Conventions
    • Labels:
      None
    • Proposal:
      Hide

      Rephrase:

      If the filter path segment appears in the resource path, the filter expression in parentheses MUST NOT use forward slashes, it must be specified with a parameter alias [link to 5.3] instead.

      Show
      Rephrase: If the filter path segment appears in the resource path, the filter expression in parentheses MUST NOT use forward slashes, it must be specified with a parameter alias [link to 5.3] instead.
    • Resolution:
      Hide

      https://github.com/oasis-tcs/odata-specs/pull/153

      Show
      https://github.com/oasis-tcs/odata-specs/pull/153

      Description

      OData-URL, section 4.12 says:

      If the filter path segment appears in the resource path and the parentheses contain a filter expression, that expression MUST NOT use forward slashes.

      Can an offending forward slash be replaced by %2f (the ABNF does not accept this at the moment)? Or must an alias be used to avoid forward slashes in paths? Clarify if necessary.

      On the other hand, the rule is too strict, because forward slashes are not a problem if the /$filter segment occurs in a URL query option, as in this test case.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              heiko.theissen Heiko Theissen
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: