CODEWITHSUNDEEP
asp.net-coreauthenticationblazor-client-side
TheAnachronism
TheAnachronism

Reputation: 185

Blazor WebAssembly Hosted Proxy crash on successful authentication

I've recently encountered quite a weird problem with my Blazor WebAssembly application in which I've used the Authorization package. Now I'm not quite sure what it is but something that authentication is doing causes the Debug proxy to crash and the browser window just closes. The only output lines I could get, which I guess have something to do with it is:

Exception thrown: 'System.Net.Sockets.SocketException' in Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.dll Exception thrown: 'System.Net.Sockets.SocketException' in System.Private.CoreLib.dll Exception thrown: 'Microsoft.AspNetCore.Connections.ConnectionResetException' in System.Private.CoreLib.dll Exception thrown: 'Microsoft.AspNetCore.Connections.ConnectionResetException' in System.Private.CoreLib.dll

I've found this GitHub issue which I think has to do something with this but I couldn't get any further solutions there...

I've tried it with different browsers to but the new Microsoft Edge as well as Chrome closes completly.

Anyone an idea why this happens?

Upvotes: 4

Views: 998

Answers (2)

Brett JB
Brett JB

Reputation: 766

Hold the Bus Originally I wrote: Ok, I think this is a 'bleeding edge' issue. If you change the server from IIS to 'your app' in the dropdown next to the green 'Debug Start' button, the the server will run standalone and hopefully circumvent some of the issues currently experienced by IIS. Its not a strict 'answer' but should hopefully be a solution... worked for me anyway.

I need to modify that answer and will leave these edits till we figure it out... I just added back some new code that I had removed, thinking they were possibly breaking changes, and it has failed again. I don't understand why since all I have put in is a static BLL Helper class and a controller for helping setup. All very so so. I have removed them again and it still doesn't work. There is a strange issue here. I'll come back when I know more. If you find anything, please post a comment.

Cheers

Upvotes: 1

TheAnachronism
TheAnachronism

Reputation: 185

Ok so something that has caused the debug browser NOT to crash is: Not using the password autocomplete for the login page. If I enter the password manually the browser doesn't crash on successful login. I have no idea how or why this works but it seems it does in some weird way.

If anyone has an idea or so please post it so I can mark it as the actual answer to this problem. This here is more of a weird workaround.

Upvotes: 2

Related Questions