I'm experiencing a service-breaking bug/issue that involves an HTTP maximum message length error.
This is the CURL command I am running, with obvious sanitation:
curl -X GET -H "X-Parse-Application-Id: <ID>" -H "Content-Type: application/json" -H "Cache-Control: no-cache" -H "Postman-Token: <TOKEN>" "https://SITEADDRESS/parse/classes/Game?where=%7B%7D&limit=400&skip=0&order=-createdAt,-createdAt"
It returns a JSON message as expected but once it reaches that maximum length (not sure what it is), I get this error (size is an example) from CURL:
(18) transfer closed with 130318 bytes remaining to read
and then the message is cut off.
If I use a smaller CURL, such as limit=40 rather than limit=400 in the URI, the data returns successfully.
This message limit seems to be at ~65k