I've noticed that sending a HTTP POST request to /workspaces with a
valid request body document leads GeoServer to return a response that
mixes a content-type of 'application/json' but a response body that is
not valid JSON (i.e., the text string with the workspace name as
specified in the response body).
This behavior causes problems in some cases. For example, some clients
use the Content-Type to pick how to handle the response body, which
includes parsing the response body with a JSON parser.
I've tested this with GeoServer 2.15.0.
Best regards,
Rui Maciel
_______________________________________________
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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
