No, there's no such configuration. As per HTTP specifications, RESTHeart returns the result of a PUT or POST via HTTP headers. This makes sense, as those are all metadata. Generally speaking, the HTTP specs try to enforce a separation between data, usually in the response body, and metadata, usually in the HTTP headers.
For example, the following curl command posts a JSON document into a MongoDB collection:
$ curl -i -H "Content-Type: application/json" -X POST http://dbapi.io/db/coll -d '{"from":"mkjsix", "message": "MongoDB rocks!"}'
HTTP/1.1 201 Created
Server: nginx/1.9.15
Date: Tue, 23 Jan 2018 16:29:31 GMT
Content-Type: application/json
Content-Length: 0
Location: http://dbapi.io/db/coll/5a6762eb74efb71411471489
Connection: keep-alive
X-Powered-By: restheart.org
Access-Control-Expose-Headers: Location, ETag, Auth-Token, Auth-Token-Valid-Until, Auth-Token-Location, X-Powered-By
Access-Control-Allow-Origin: *
ETag: 5a6762ebc9e77c0007974479
Access-Control-Allow-Credentials: true
As you can see, the Location
header contains the URI of the newly created document, which actually ends with the object id, as generated by MongoDB. If you instead use the PUT verb, then you are providing the id by yourself.