olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bolz (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OLINGO-752) Add support for "+" sign as a separator in addition to %20 for URLs
Date Sat, 23 Sep 2017 11:41:00 GMT

     [ https://issues.apache.org/jira/browse/OLINGO-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Bolz closed OLINGO-752.
-------------------------------

> 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)

Mime
View raw message