-
Notifications
You must be signed in to change notification settings - Fork 92
Description
We're leveraging version 2.26.x for Geoserver Cloud and are experiencing the following behaviors when trying to leverage SLD Styling. We are providing the sld body and CQL Filter as a x-form-url-encoded POST with success in version 2.17.x. However when attempting to do so within geoserver-cloud 2.26.x with the following request as POST, utilizing a custom_style.ysld leveraging the sld body documentation for 2.26.x,
API Call without root url, successful 200 for both version=1.1.1 and 1.3.0:
/wms?REQUEST=GetMap&SERVICE=WMS&VERSION=1.13.1&FORMAT=image/png&CRS=EPSG%3A3857&STYLES=style_name_YSLD&LAYER=WORKSPACE:LAYER_NAME
Which responds with
<?xml version="1.0" encoding="UTF-8"?>
<ServiceExceptionReport version="1.3.0" xmlns="http://www.opengis.net/ogc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ogc https://cng-api.a-np.location360.ag/geoserver-cloud/schemas/wms/1.3.0/exceptions_1_3_0.xsd">
<ServiceException>Unknown layer: WORKSPACE:LAYER_NAME</ServiceException>
</ServiceExceptionReport>I have confirmed via the UI that previews for WMS and WFS are working appropriately for our options being utilized (image/png, OpenLayers and application/json respectively)
The following form_data.txt contains 2 key value pairs for CQL_FILTER and SLD_BODY parameters, with a CQL Filter that previously are successful in returning WMS images on Geoserver 2.17.x