You are right: not a bug in GeoServer but a consequence of XML the developper needs te be aware of. I’m not too familiar with XML. The lesson I took from it that it is better to use json in the body of the request. Very nice that GeoServer supports both.
Best regards, Bart
Ian Turton
July 16, 2021 at 9:58 AM
That would be invalid XML - what happens if you use & instead if &
POST /workspaces/{workspaceName}/datastores
This payload in the REST request leads to a 500 status, caused by password:
<dataStore>
<name>store_a</name>
<connectionParameters>
<host>localhost</host>
<port>5432</port>
<database>db1</database>
<user>postgres</user>
<passwd>&</passwd>
<dbtype>postgis</dbtype>
</connectionParameters>
</dataStore>