[
https://issues.apache.org/jira/browse/OLINGO-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968072#comment-15968072
]
Ramesh Reddy commented on OLINGO-1107:
--------------------------------------
[~mirbo] This always in encoding side, as long as decoding side can handle both
+ and %20 we will be fine. We know that %20 is already handled in server, +
may not be handled as noted as in OLINGO-752 for possible issues. In this
particular issue client may be inadvertently passing + instead of %20, which
will be corrected with the patch
> UriDecoder should use java.net.URLDecoder
> -----------------------------------------
>
> Key: OLINGO-1107
> URL: https://issues.apache.org/jira/browse/OLINGO-1107
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.3.0
> Reporter: Jon McEwen
>
> Query filters are incorrectly parsed, because the
> org.apache.olingo.commons.core.Decoder doesn't convert '+' to space.
> Simple fix is to use java.net.URLDecoder instead (line 85):
> {{return URLDecoder.decode(encoded, "UTF-8");}}
> Additional unit test:
> {code:Java}
> @Test
> public void decodePlusAsSpace() throws Exception{
> checkOption("%24filter=PaymentStatus+eq+%27Cleared%27", "$filter",
> "PaymentStatus eq 'Cleared'");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
