$refs failed to resolve with such error: "Could not resolve reference: Failed to execute 'delete' on 'Headers': Headers are immutable"

[PatchRanger]

OS: Ubuntu 22.04.1
Browser: Chromium-based
Version 108.0.0.0
Method of installation: via docker image swaggerapi/swagger-ui
Swagger-UI version: v5.0.0-alpha.4
Swagger/OpenAPI version: 3.1.0

The installation is the same as in #8525 (comment).

After I successfully applied the workaround about absolute paths for $ref, I see in the browser console that requests for schemas began to go to the correct host - and even return with a 200 response.
But I found another problem: $ref inside uploaded documents refuse to load, I see a lot of red error messages with the following text:

Resolver error at $ref
Could not resolve reference: Failed to execute 'delete' on 'Headers': Headers are immutable

I see nor errors in the browser console neither non-ok requests in its Network tab.

In addition, when I click on the dropdown arrow next to each operation, the operation dropdown does not drop out - just the dropdown arrow changes to "open" and that's it. I believe this is related: apparently due to the fact that $ref has not loaded, there is nothing to show in the operation dropdown.

Perhaps the reason for this is the same as in the previous issue: incorrect resolution of relative paths. I hope that after fixing that problem, this problem will also go away. But perhaps this is not related, I do not have enough SwaggerUI context to judge with complete confidence - therefore, I am creating this issue in order to inform the development team about the difficulties that arise.

[PatchRanger]

[char0n]

#8525 was resolved in #8533 and is unrelated to this issue.

[char0n]

The issue is in again in swagger-client on this line.

[char0n]

Headers are immutable and thus we cannot remove headers from it. This works in node-fetch but doesn't work in browsers.

To fix this, we have to clone the response in order to mutate it.

More info in https://developer.mozilla.org/en-US/docs/Web/API/Headers

[char0n]

Further context: we're removing Content-Type header from the HttpSwaggerClient ApiDOM resolver plugin to avoid serialization into JSON/YAML. HttpSwaggerClient needs to return buffer and serializing into JSON/YAML and then returning buffer would only make the resolution slower.

[char0n]

Addressed in upstream: swagger-api/swagger-js@1df6b38

[PatchRanger]

@char0n Wow, I am impressed, blazingly fast debug & fix, thank you! I am going to check whether it fixes this issue (I am prettty sure it should).

[char0n]

Addressed for swagger-ui@5 in #8536

[char0n]

@char0n Wow, I am impressed, blazingly fast debug & fix, thank you! I am going to check whether it fixes this issue (I am prettty sure it should).

Release will be comming in an half an hour. Please keep the issues related to OpenAPI 3.1.0 comming. OpenAPI 3.1.0 support in swagger-ui@5 is current priority and I appreciate any early feedback that you provide.

[char0n]

Released as https://github.com/swagger-api/swagger-ui/releases/tag/v5.0.0-alpha.5