HTTPRequest fails HEAD mode requests in Chrome 113

[Isaaaca]

Godot version

v3.5.2.stable.official [170ba33]

System information

Chrome Version 113.0.5672.64 (Official Build) (64-bit), Microsoft Edge Version 113.0.1774.35 (Official build) (64-bit)

Issue description

After Chromium 113, http requests with the HEAD method returns a response with an null body. This results in a TypeError in html5 exports, which causes HTTPRequest nodes to return a RESULT_CONNECTION_ERROR with a response code of 0. So far this affects all Chromium browsers, Firefox and Safari have not been affected (based on my limited testing). I suspect the problem to affect the HTTPClient node as well, but I have not tested that yet.

TypeError and Variables returned from 'request_completed' signal

Response object with body being null in Chrome 113

Response object in Firefox and older Chromium Browsers

I believe the js error is caused by this bit of code in the .js export:

But re-writing that bit so that obj.reader is null, undefined or new ReadableStream().getReader() only suppresses the error and does not solve the problem.

Steps to reproduce

1. Create a HTTPRequest node
2. Make a (valid) request with the HEAD method.
3. Export the project to HTML5
4. Run the project in any Chromium browser based on Chromium 113

Minimal reproduction project

HTTPRequestMRP.zip

[Calinou]

Can you reproduce this in Chromium 112 or older?

[nullyfae]

@Calinou maybe you wanna see this issue microsoft/typed-rest-client#355

[Isaaaca]

Can you reproduce this in Chromium 112 or older?

No, it only occurs in Chromium 113.0.5672.64. Our project started having problems since last week's (2 May) update to the version.
https://chromereleases.googleblog.com/2023/05/stable-channel-update-for-desktop.html

Good news is, it seems this has been just been reverted.
https://chromereleases.googleblog.com/2023/05/stable-channel-update-for-desktop_8.html

from: https://chromium.googlesource.com/chromium/src/+log/113.0.5672.63..113.0.5672.92?pretty=fuller&n=10000

However, it might still be worth fixing since having a response with a null body does comply to standard.

https://fetch.spec.whatwg.org/#responses

[lodicolo]

Because of the aforementioned revert this isn't happening in Chromium (127.0.6533.72), but does currently happen on Firefox (131.0.3) for HEAD requests (and presumably for any empty responses for other HTTP methods).

I traced it down to library_godot_fetch.js#L62 and I opened PR #98431 as a possible minimally invasive solution.