Accessing WMS via http-proxy

[Nahuel Iglesias]

Hi @all, greetings from Argentina

I'm working with GeoServer an Mapstore on 2 different Docker containers.

Container names are "geoserver" and "mapstore" (I'm super creative, I know). So, the Mapstore container can resolve the Geoserver container's IP using "geoserver" as name.

I can access WFS data stored on Geoserver from Mapstore by adding the service in Mapstore's catalog using:

http://geoserver:8080/geoserver/wfs

As I can see from the browser developer's console, the Mapstore frontend is accessing this data using http-proxy and all works OK.

BUT: when I try to acces WMS data, using:

http://geoserver:8080/geoserver/wms

in the browser console I see Mapstore accessing WMS "GetCapabilities" request using http-proxy:

http://<MAPSTORE-SERVER>/mapstore/proxy/?url=http://geoserver:8080/geoserver/wms?service=WMS&version=1.3.0&request=GetCapabilities

So far so good. I can search for WMS layers and get a listing.

Then, when I select and add a layer to the Mapstore map, the following happens:

 - "DescribeLayer" request is correctly retrieved using http-proxy

http://<MAPSTORE-SERVER>/mapstore/proxy/?url=http://geoserver:8080/geoserver/wms?service=WMS&version=1.1.1&request=DescribeLayer&layers=<LAYER_NAME>

- "GetMap" request is NOT using http-proxy and tries to access the Geoserver directly, which obviously is not resolving the "geoserver" name as it is unkown by that name outside the Docker network, and so the request fails and no image is shown on the map:

http://<MAPSTORE-SERVER>:8080/geoserver/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=<LAYER_NAME>

(URL abbreviated for simplicity)

I could not find any documentation on how to configure what information the front-end should retrieve using http-proxy and what other information directly.

Where should I look at? How can I have ALL requests to "geoserver" go through http-proxy?

[Lorenzo Natali]

Hi, 

MapStore uses the proxy only when necessary. 

In particular it is used only when the request is not allowed by the same origin policy. 

Images do not have this restriction, so they are not proxied at all. 

I suggest instead to expose geoserver to the path "/geoserver" and mapstore to the path "/mapstore" on same port ( 80 or whatever) of a 3rd nginx or apache docker instance.

So you can configure the catalog as "/geoserver/" (relative URL) and avoid the proxy at all for your application.

Don't forget to set geoserver proxy base URL accordingly to allow to properly generate capaiblities document with the correct domain. 

This helps also to port the installation between different  domains. 

[Nahuel Iglesias]

Hi,

This worked like a charm - thanks!

[Steven Graham]

Would have a a copy of the compose file that you have working? I have not been able to get a working compose file with both geoserver and mapstore.