Navigation error when using WV2 to connect to Blazor server app #4528
Replies: 1 comment
-
Here's the request and response detail from customer purchase when the 500 server error is returned Actual headers sent with request Headers in response received when I run test purchases I get this Actual headers sent with request Headers in response received Still can't track the problem down, although it does look as though the server is blocking the requests. It may be a regional problem as customer error reports I'm getting are all from non UK locations. Any insights ? |
Beta Was this translation helpful? Give feedback.
-
I've been using WV2 for a couple of years to connect customers running my C# apps to purchase/register the apps on my site. All worked well under Net7.
Recently I upgraded my apps and the site to net8. Since then I've been getting reports of navigation failure 500 errors with Status code "Unknown" being logged in my CoreWebView2_NavigationCompleted handler. Customers say they can't connect to the landing page on my site although the page loads fine with same query string in Firefox, Edge and Chrome.
I can also complete end to end test purchases both on IIS and the remote server so it looks as though the issue is WV2/Net8 specific. I'm running WV2 1.0.2365.46 on Net8 and the site is a Blazor server app.
It's not an anti-virus issue as customers report they still can't connect with av switched off.
I've tried various "fixes" including adding this code to program.cs in the server app:
builder.Services.AddCookiePolicy(options=> { options.MinimumSameSitePolicy = SameSiteMode.None; });
which should revert cookie handling to the Net7 policy, but seems to have no effect.
Any insights much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions