### Describe the bug

A logon sequence works perfectly well with axios v1.1.3
Changing nothing more than axios from v1.1.3 to 1.2.0 now results in 401 Unauthorized

### To Reproduce

Unfortunately, I cannot reveal the entire log for security reasons
I have studied the detailed axios interceptor logs of a successful v1.1.3 vs failed v1.2.0 session
I have seen the following major difference

1.1.3:  response data is logged as plain text, Logging using axios interceptiors:
  data: '<!DOCTYPE HTML>\r\n' +
    '<html lang="en">\r\n' +
    '<head>\r\n' +


1.2.0: response data is not decoded when logged, Logging using axios interceptiors:
  data: '\x1F�\b\x00\x00\x00\x00\x00\x00\x03�=ks�Fr߯���\x18�ZJ�@\x12|��J\x1B���*��U��c;�\x010 g\x05`p\x00(�v\\�����_��\x19�\b�"���%�e�\x04���ӯ��\x01_\x7F��ǣ�\x1Fώɻ���\x07\x7F���q�{ģ�h_c�&�0���



### Code snippet

_No response_

### Expected behavior

I expect v1.2.0 to work same as v1.1.3 after an upgrade from 1.1.3 to 1.2.0

### Axios Version

1.2.0

### Adapter Version

http

### Browser

n/a, this is a logon sequence to connect to a device via http

### Browser Version

_No response_

### Node.js Version

18.12.1

### OS

Microsoft Windows 10 Home (10.0.19045)

### Additional Library Versions

```bash
"axios-cookiejar-support": "^4.0.3",
"axios": "=1.1.3", // 1.2.0 fails
"mqtt": "^4.3.7",
"qs": "^6.11.0",
"tough-cookie": "^4.1.2"
```


### Additional context/Screenshots

_No response_
lib/adapters/http.js
config,
          req
        ));
        abort();
      });
    }
    
    if (utils.isStream(data)) {
      let ended = false;
      let errored = false;
      data.on('end', () => {
        ended = true;
      });
      data.once('error', err => {
        errored = true;
        req.destroy(err);
      });
      data.on('close', () => {
        if (!ended && !errored) {
          abort(new CanceledError('Request stream has been aborted', config, req));
        }
      });
      data.pipe(req);
    } else {
      req.end(data);
    }
  });
}
export const __setProxy = setProxy;