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:
Accept-Encoding: Identity (without this parameter)
With Headers I've tried different combinations, including image/jpeg,
image/png - neither worked for me.


Configuration in API-gateway was done according to this tutorial

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

Endpoint response headers: {Date=Tue, 29 Jan 2019 14:34:11 GMT,
Content-Type=image/jpeg, Transfer-Encoding=chunked, Connection=keep-alive,
Expires=Tue, 05 Feb 2019 14:34:11 GMT; Path=/, X-Frame-Options=SAMEORIGIN,
Access-Control-Allow-Origin=*, Content-Disposition=inline;

Any advice is appreciated.
Thank you

Sent from:

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:
- The GeoServer user list posting guidelines:

If you want to request a feature or an improvement, also see this:

[hidden email]