[ https://issues.oasis-open.org/browse/ODATA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67072#comment-67072 ]
Ralf Handl commented on ODATA-1101:
-----------------------------------
Only the first occurrence of a question mark and a hash character have special meaning, after that they can occur unencoded.
So we can use clear-text question marks within query and fragment, but not in the path part.
And we can use clear-text hash characters within the fragment, but not in the path and query parts.
> The hash (#) character is not allowed in search phrases per the ABNF definition
> -------------------------------------------------------------------------------
>
> Key: ODATA-1101
> URL: https://issues.oasis-open.org/browse/ODATA-1101
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: ABNF Construction Rules
> Affects Versions: V4.01_CSD02
> Reporter: Mark Biamonte
> Fix For: V4.01_CS01
>
>
> The hash character (#) has meaning in both a URL and in OData so it makes sense that the hash character is not allowed in a search word. I would have expected though that the hash character could be used in a quoted search phrase, but the ABNF definition for search phrase does not include the hash character.
> searchPhrase = quotation-mark 1*qchar-no-AMP-DQUOTE quotation-mark
> qchar-no-AMP-DQUOTE = qchar-unescaped
> / escape ( escape / quotation-mark )
> qchar-unescaped = unreserved / pct-encoded-unescaped / other-delims / ":" / "@" / "/" / "?" / "$" / "'" / "="
> unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
> other-delims = "!" / "(" / ")" / "*" / "+" / "," / ";"
> None of those definitions include the hash character. Was the hash character left out on purpose? Is the only way to include it to percent encode it?
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
