Clientless Flurl from inside Blazor WASM gives 'opaqueredirect' and makes no actual call

[mennowo]

Given the following call from inside a Blazor WebAssembly app

var response = await configuration.Endpoint
    .AppendPathSegment(endpoint)
    .WithHeader("api-version", "1.0")
    .PutJsonAsync(item)
    .ConfigureAwait(false);

the endpoint seems not to be actually called (breakpoint in API is not hit; on the other hand, get endpoints do work). The response has succes code 0 and reasonphrase 'opaqueredirect'. Is this expected behaviour in this context? That is, is the clientless pattern not fit for using in Blazor WASM?

I have extensively searched but have been unable to find definitive information. There is for example this, would that be the way to go? This would involve extensive refactoring in my code, so the clientless pattern would be preferable; however, if for some reason this is not possible, this is also good to know.

Happy to have any input. Feel free to close this as a non-issue in case I am simply overlooking some documentation here.