[ 
https://issues.apache.org/jira/browse/OLINGO-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119572#comment-16119572
 ] 

Archana Rai commented on OLINGO-752:
------------------------------------

This issue has been fixed in v4 with the commit:
 
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=38f77daa5c555af2012449e1f090a0395bd7a883
and in v2 with this commit: 
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=070090eada88ce9b4c886cc6d30043654995f869.

Please verify if the fix is fine for you and get back.

Thanks,
Archana


> Add support for "+" sign as a separator in addition to %20 for URLs
> -------------------------------------------------------------------
>
>                 Key: OLINGO-752
>                 URL: https://issues.apache.org/jira/browse/OLINGO-752
>             Project: Olingo
>          Issue Type: New Feature
>          Components: odata2-core
>    Affects Versions: V2 2.0.4, (Java) V4 4.0.0-beta-03
>            Reporter: Ronny Bremer
>            Priority: Minor
>         Attachments: 0002-OLINGO-752-Treat-as-space-in-Decoder.patch
>
>
> Some well-known OData client libraries, such as JQuery, are using the 
> incorrect encoding for URLs sent to OLingo based OData v2 services.
> According to the OData V2 standard, the separator for encoded URLs is %20.
> However, in many cases when developers talk about "URL encoding", they use 
> Java functions like "URLEncoder.encode()" to encode the parameters for their 
> HTTP request. JQuery seems to utilise a similar function in JavaScript.
> Now these functions are based on the HTTP forms encoding standard, so they 
> use "+" as a separator.
> If would be small but grateful addition to the OLingo URI parser to accept 
> both separator characters. Maybe with a config option to follow the standard 
> (so only accept %20) or to be more relaxed (and accept both).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to