iOS SDK makes frequent queries to parse-server with a Content-Length and empty POST body

[woodardj]

Several times per minute, we see queries to our Parse Server which have non-zero Content-Length headers set, but which have empty body. This causes Parse Server to stall out while waiting for data. I have an issue filed over there as well, in case it's an issue that can be corrected server side. (https://github.com/parse-community/parse-server/issues/4068)

However, these are almost always iOS devices making these bad queries (our iOS and Android apps use different subdomains to reach the same server), and they are always to /parse/classes/:class/:classID queries/routes being requested via the SDK's findInBackground.

We see this on 'X-Parse-Client-Version', 'i1.15.3' and all previous versions.

Anyone else have this experience? Is there a way we could fix this in our App code? I'm sort of at a loss.

[flovilmart]

@woodardj can you pinpoint which call in the SDK is doing so and provide steps to reproduce?

[woodardj]

I'm afraid I can't at the moment. Is it possible that poor network performance (or carrier drops) could be causing this? It's pretty frequent, and I'd be surprised if it were just us. iOS is also not my specialty, so I'm not even sure what to look for.

But I can say this seems to happen most frequently with _Installation requests.

[noobs2ninjas]

This still an issue with the latest version?