fix(sdk-middleware-http) Remove dependence on content in ok result

It's not uncommon to use return `Accepted()` or return `Ok()` in asp core and even though specifying the content type the return will be empty making json() throw. The content length header is stripped in the proxy so the simplest solution for handling a common server solution for empty 202 and 200 seems to be to catch the exception and continue with an empty body.

Author: Olof Moriya

packages/sdk-middleware-http/src/http.js

@@ -146,10 +146,10 @@ export default function createHttpMiddleware({
                 return
               }
 
-              res.json().then((result: Object) => {
+              res.text().then((result: Object) => {
                 const parsedResponse: Object = {
                   ...response,
-                  body: result,
+                  body: result.length > 0 ? JSON.parse(result) : {},
                   statusCode: res.status,
                 }
 

packages/sdk-middleware-http/test/http.spec.js

@@ -952,4 +952,34 @@ describe('Http', () => {
 
       httpMiddleware(next)(request, response)
     }))
+
+  test('execute a post request with empty 202 response', () =>
+    new Promise((resolve, reject) => {
+      const request = createTestRequest({
+        uri: '/foo/bar',
+        method: 'POST',
+      })
+      const response = { resolve, reject }
+      const next = (req, res) => {
+        expect(res).toEqual({
+          ...response,
+          body: {},
+          statusCode: 202,
+        })
+        resolve()
+      }
+      // Use default options
+      const httpMiddleware = createHttpMiddleware({
+        host: testHost,
+        fetch,
+      })
+      nock(testHost)
+        .defaultReplyHeaders({
+          'Content-Type': 'application/json',
+        })
+        .post('/foo/bar')
+        .reply(202, undefined)
+
+      httpMiddleware(next)(request, response)
+    }))
 })