[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-565) 2: Clarify interpretation of path segments and query option values with respect to percent-encoded punctuation
[ https://tools.oasis-open.org/issues/browse/ODATA-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-565: ----------------------------- Environment: [Applied] > 2: Clarify interpretation of path segments and query option values with respect to percent-encoded punctuation > -------------------------------------------------------------------------------------------------------------- > > Key: ODATA-565 > URL: https://tools.oasis-open.org/issues/browse/ODATA-565 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData ABNF Construction Rules, OData URL Conventions > Affects Versions: V4.0_CS02 > Environment: [Applied] > Reporter: Ralf Handl > Assignee: Ralf Handl > Fix For: V4.0_ERRATA01 > > > Chapter 2 states the parsing rules for OData URLs. Unfortunately the last of the six rules > - Interpret path segments, query option names, and query option values according to OData rules > is rather fluffy and leaves it to the reader to decide what the "OData rules" are. > Later sections mainly refer to the ABNF, and the ABNF accepts percent-encoded values for most of the OData-significant delimiters in section 9. Punctuation. > This in conjunction with the fifth parsing rule > - Percent-decode path segments, query option names, and query option values > may mislead implementers into double-decoding OData delimiters. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]