fixing content-type header bug in 204 response parsing

patrick-rodgers · Jun 3, 2024 · cc1e8ba · cc1e8ba
1 parent 74f1783
commit cc1e8ba
Showing 1 changed file with 1 addition and 3 deletions.
diff --git a/packages/graph/batching.ts b/packages/graph/batching.ts
@@ -375,8 +375,6 @@ function parseResponse(graphResponse: IGraphBatchResponse): ParsedGraphResponse
         // the array of requests and make it easier to map them by index
         const responseId = parseInt(response.id, 10) - 1;
 
-        const contentType = response.headers["Content-Type"];
-
         const { status, statusText, headers, body } = response;
 
         const init = { status, statusText, headers };
@@ -397,7 +395,7 @@ function parseResponse(graphResponse: IGraphBatchResponse): ParsedGraphResponse
             // eslint-disable-next-line @typescript-eslint/dot-notation
             parsedResponses[responseId] = new Response(jsS({ location: headers["Location"] || "" }), init);
 
-        } else if (status === 200 && /^image[\\|/]/i.test(contentType)) {
+        } else if (status === 200 && /^image[\\|/]/i.test(headers["Content-Type"] || "")) {
 
             // this handles the case where image content is returned as base 64 data in the batch body, such as /me/photos/$value (https://github.com/pnp/pnpjs/issues/2825)