Latest version of .net8, CMS 12.28, FIND 16.1MVC + Blazor + FIND
//runs on click thru blazor socket magic, in a blazor component server side var searchResult = client.Search<ArticlePage>().GetContentResult();
We had version FIND 16.0 that has this bug, in version 16.1 and 2 it is solved.
Latest version of .net8, CMS 12.28, FIND 16.1
MVC + Blazor + FIND
In log:System.Net.Http.HttpClient.HttpClientWithAutoDecompression.ClientHandler: Information: Sending HTTP request POST https://demo02.find.episerver.net/ZLs1....pKmzUWRa/gosso_20240326/_search
My guess is that the Blazor Server scope then the whole session is in a SignalR connection and you probably get things added for a traditional MVC request that FIND is needed.