[
https://issues.apache.org/jira/browse/OLINGO-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206432#comment-14206432
]
Michael Bolz commented on OLINGO-480:
-------------------------------------
Hello [[email protected]],
I took a look into [URI Conventions for OData
V2|http://www.odata.org/documentation/odata-version-2-0/uri-conventions#UriEquivalence].
There is recommended that *each URI SHOULD be normalized using the rules
specified in \[RFC3987\] and \[RFC3986\]*.
And in [RFC3986 - Section 2|http://tools.ietf.org/html/rfc3986#section-2] only
*percent encoding* is listed.
Based on that Olingo only supports percent encoding of the URL.
And as you mentioned in the description the {{Decoder}} is not the correct
place for the {{+}} replacement.
For my understanding, what is your use case that you need {{+}} instead of
{{%20}}?
Kind regards,
Michael
PS: sorry that I have overlooked the part with the right place at first
> good old '+' as a encoding for a space is not handled in Decoder class
> ----------------------------------------------------------------------
>
> Key: OLINGO-480
> URL: https://issues.apache.org/jira/browse/OLINGO-480
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.1
> Reporter: Giacomo Pati
> Assignee: Michael Bolz
> Fix For: V2 2.0.2
>
> Attachments: 0001-Change-Decoder-class-to-respect-also-as-space.patch
>
>
> A request like wget
> http://localhost:8080/SalesOrderProcessing.svc/SalesOrderItems?$filter=Delivered+eq+true
> should be accepted as commonly a '+' is encoding a space. The Decoder class
> so far only decodes percent-encoded values and leaves the plus sign as is.
> The applied patch adds this decoding to the Decoder class (maybe it's not the
> right place to put it but I was not able to find any other place)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
