[GTLRService responsePartWithMIMEPart:] sets error for "204 No Content" responses

[jgheab]

Repro steps:

1. Call [GTLRService responsePartWithMIMEPart:] passing a GTMMIMEDocumentPart instance where the body property is set to:

HTTP/1.1 204 No Content
ETag: ""
Date:
<CRLFCRLF (must end in "\r\n\r\n" with no additional data)>

Expected:
The returned GTLRBatchResponsePart instance should not have its parseError or JSON properties set, since no error occurred and no content was returned.

Actual:
parseError is set.
Domain: "com.google.GTLRServiceDomain" (kGTLRServiceErrorDomain).
Code: -3001 (GTLRServiceErrorBatchResponseUnexpected).

[thomasvl]

Can you provide some more details? Normally there are also headers on the mime part which would include a Content-ID, etc. It helps to know we're looking at the same setup.

Edit: Exactly where else there are CRLFs vs. just CR or LF could also come into play here.

[thomasvl]

If my guess is correct, a little more about what is happening in this batch might help. I'm guessing you are making multiple request, and one part is succeeding, but with no new content (because of the ETag)? So this this likely isn't just about this parse being correct, but also ensuring everything else "works" in the case for the batch.