AWS API-gateway and Geoserver, issues with WMS

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

AWS API-gateway and Geoserver, issues with WMS

GeoServer - User mailing list
Hi all,

I'm trying to integrate AWS api-gateway with Geoserver that is also
installed on AWS.

On Api-Gateway level I've created few HTTP_PROXY resources, each for each
geoserver protocol (wms,wfs, wps, etc.).

Proxied WFS request works well with JSON output.

I currently experience an issue with WMS output.

Here is my request example:
Headers:
Accept:image/*
Content-Type:image/*
Accept-Encoding: Identity (without this parameter)
With Headers I've tried different combinations, including image/jpeg,
image/png - neither worked for me.

URL:
https://${gatewayId}.execute-api.{region}.amazonaws.com/prod/geo/map?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image/jpeg&TRANSPARENT=true&LAYERS={myLayer}&exceptions=application/vnd.ogc.se_inimage&SRS=EPSG:3857&STYLES={mystyle}&WIDTH=512&HEIGHT=512&BBOX=-12634495.0382586,6682245.65877462,-12631901.2941232,6684794.46255934&TIME=2017-07-18T18:29:19Z

Configuration in API-gateway was done according to this tutorial
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-payload-encodings-configure-with-console.html

Response has 200 status, but image is not readable in any image viewer.
Without Accept-Encoding: Identity size of output is about 4kb and with
Accept-Encoding: Identity size is about 8 kb.

API gateway logs:

Endpoint response body before transformations: ����JFIF��C
...
E` [TRUNCATED]

Endpoint response headers: {Date=Tue, 29 Jan 2019 14:34:11 GMT,
Content-Type=image/jpeg, Transfer-Encoding=chunked, Connection=keep-alive,
Set-Cookie=AWSALB=q5/1VFZnzVMM3XV2EuOn9nqi0i7ANBPYTxltXi7dI6K/9WK0RjCPUDbGgL9I3Axy7ad7EyJC4h5mPRWMODtsatUOY/FKsddsgAKF8mYy3hW8th3RjulQktQTQmx9UuVt;
Expires=Tue, 05 Feb 2019 14:34:11 GMT; Path=/, X-Frame-Options=SAMEORIGIN,
Access-Control-Allow-Origin=*, Content-Disposition=inline;
filename=my-layer.jpg}

Any advice is appreciated.
Thank you





--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html


_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users