[Geoserver-devel] [JIRA] (GEOS-8480) Mapfish print module : sending a POST request, then changed in GET ?

Jean-Christophe Bastin created an issue

GeoServer / BugGEOS-8480

Mapfish print module : sending a POST request, then changed in GET ?

Issue Type:

BugBug

Affects Versions:

2.11.1

Assignee:

Unassigned

Components:

Mapfish print, WMS

Created:

08/Dec/17 1:32 PM

Environment:

Windows 10
Oracle Spatial Database for vectorial data
Some external WMS coming from MapServer or OSM

Priority:

HighHigh

Reporter:

Jean-Christophe Bastin

I first posted this issue on https://github.com/mapfish/mapfish-print, but they told me that it’s a Geoserver issue. I got the answer “You POST request is sent to GeoServer, then it’s GeoServer choosing to do a GET to MapFish Print”.

Here is the initial explanation :

Hello everyone,

I have an issue with the size of my print request.
I send a POST http request because I know that the spec parameter can be
really big (I have a custom parameter CQL_FILTER to filter some layers to
print). The POST request is well sent with “/geoserver/pdf/create.json”.
When I check the generated PDF, I get an empty map with the following error
near the zone of the map : “Error java.io.IOException : Error (status=414)
while reading the image from [http://…(the](http://…(the) rest of the big url)…”.

When I check the log file of GeoServer, I see the same error : “ERROR
[print.PDFUtils] - Server returned an error for [http://…(the](http://…(the) rest of the
big url)… : Request-URI Too Large”

I understand the error, URI too long, but why my POST request is finally
converted in GET request to retrieve the image of my report ? Why doesn’t it
stay in POST request ? Do I have to configure something in the print plugin
?

Any help appreciated.

Kind regards,

JCB

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS


This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074-sha1:b69b2a5)

Atlassian logo