You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Ricky Li (Jira)" <ji...@apache.org> on 2020/08/14 02:34:00 UTC

[jira] [Updated] (OLINGO-1476) AsyncRequestWrapperImpl failed to process relative URL in Location header.

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

Ricky Li updated OLINGO-1476:
-----------------------------
    Priority: Critical  (was: Major)

> AsyncRequestWrapperImpl failed to process relative URL in Location header.
> --------------------------------------------------------------------------
>
>                 Key: OLINGO-1476
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1476
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client
>    Affects Versions: (Java) V4 4.7.1
>            Reporter: Ricky Li
>            Priority: Critical
>
> For async OData request, if a relative URL(such as: ../../_async('EQ1XW')) is returned from server side, an exception will be reported by _AsyncRequestWrapperImpl.checkLocation_ function.
> I think that should be a 'shortcoming' of OLingo, not only are relative URLs allowed/supported according to the OData standard, better yet they SHOULD be relative for the sole reason that often the server maybe work behind a proxy, which resides at a different URI, likely on a different HOST, most likely running on a different port and most definitely accepting request on a different service root path. 
> Relative URLs, part of the HTTP standard on which OData, are exactly there to make these transitions easy.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)