olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Tretyakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLINGO-752) Add support for "+" sign as a separator in addition to %20 for URLs
Date Mon, 06 Nov 2017 10:41:00 GMT

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

Dmitry Tretyakov commented on OLINGO-752:

[~archanarai] [~chrisam], this fix works, but enabling this mode via query parameter does
not work in our case, because we could not rewrite all clients of OData2 feed.

In my mind the better way to enable this mode would be to use http request attribute like
`org.apache.olingo.odata2.path.split` or Java system property.

> 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

View raw message