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

Jens Huesken commented on OLINGO-126:
-------------------------------------

Hi Miki,
I am not sure that your requirement can be met by further configuration on the 
Apache HTTP Server.

The OData library does not support this use case explicitely by setting a 
runtime property either via coding or configuration.

What might work in your scenario is that you pass the URI at the EntityProvider 
by calling e.g. writeFeed and passing the required URI via 
EntityProviderWriteProperties.

public static ODataResponse writeFeed(
      final String contentType,
      final EdmEntitySet entitySet,
      final List<Map<String, Object>> data,
      final EntityProviderWriteProperties properties)
      throws EntityProviderException

URI serviceRoot = new URI("http://localhost:80/";);
EntityProviderWriteProperties properties = 
EntityProviderWriteProperties.serviceRoot(serviceRoot).build();

Regards,
Jens.

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

Reply via email to