Ivan Shynkarenka
Ivan Shynkarenka
Because you need to pass correct DNS name without routes and protocol name: wss://customserver.com/web_socket -> customserver.com
It is possible for super optimized projects, but it's not a common .net core cross-platform way.
If no Content-Length is provided in DELETE request, then at least "\r\n\r\n" should be provided at the end to detect end of request.
``` Windows and macOS do not yet support TLS 1.3. .NET Core 3.0 will support TLS 1.3 on these operating systems when support becomes available. ``` https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#tls-13--openssl-111-on-linux
Will wait for .NET Core support TLS 1.3 on all systems.
.NET 6 covers TLS 1.3 for Linux & Windows platforms, but still not MacOS: ``` Moreover, MacOS is not supported at all since its security layer doesn’t provide either of...
.net 6 is now supported
It seems that your server generates much more data, than client can handle. As the result your buffers grows. Your client and server should be balanced, and your server should...
Please try: ``` protected override void OnReceivedRequest(HttpRequest request) { // Prepare the response Response.Clear(); Response.SetBegin(200); Response.SetHeader("Access-Control-Allow-Origin", "*"); Response.SetBody(); // Send the response SendResponseAsync(Response); } ```
No it's not. We use HttpSession.Response just as "always existing" object in `OnReceivedRequest()` hanlder. You can create a new Response object if you like.