Jan 17, 2019 06:43 PM|eeldivad|LINK
I found the solution. It was quite easy with one line in the Startup class. This removes the limit by setting it to null. I know it's not best practice but this is an intranet app where I control the client code so I'm not worried since I only need large
messages less than 1% of the time.
GlobalHost.Configuration.MaxIncomingWebSocketMessageSize = null;