You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "M Carissimi (JIRA)" <ji...@apache.org> on 2014/02/24 13:45:20 UTC
[jira] [Closed] (OLINGO-126) Use of an OData service behind an
Apache reverse proxy
[ https://issues.apache.org/jira/browse/OLINGO-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
M Carissimi closed OLINGO-126.
------------------------------
> Use of an OData service behind an Apache reverse proxy
> ------------------------------------------------------
>
> Key: OLINGO-126
> URL: https://issues.apache.org/jira/browse/OLINGO-126
> Project: Olingo
> Issue Type: Question
> Affects Versions: V2 1.0.0
> Reporter: M Carissimi
> Assignee: Stephan Klevenz
> Fix For: V2 1.2.0
>
>
> Hello,
> we have an OData service built on Olingo which we package in a web archive running a CXFNonSpringJaxrsServlet. The module is deployed to a Glassfish 3.1.2.2 domain which sits behind an Apache HTTP server with reverse proxy capabilities. The Apache 2.2 virtual host configuration has the following entries:
> ProxyPass /olingo http://appsdev1:10156/ODataPrototypeOlingo
> ProxyPassReverse /olingo http://appsdev1:10156/ODataPrototypeOlingo
> Using this configuration we can successfully access the OData service using URL:
> http://server/olingo/service.svc/entityset
> The feeds that we get back from the service contain links with URLs for the actual server running Glassfish:
> http://appsdev1:10156/ODataPrototypeOlingo/service.svc/entityset
> Is there a way to dynamically change the links generated in Olingo to use the root URL used in the request so that links have URLs similar to:
> http://server/olingo/service.svc/entityset
> Regards
> Miki
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)