0 votes
by (1.7k points)

I just downloaded the Rebex's WebSocketClient Beta version and made the test simpler.

When the WebSocketClient.ConnectAsync function is called, the following exception occurs.

"The server returned status code '301' instead of '101'."
All of the basic WebSocketClient works properly.

Thank you.

Applies to: Rebex WebSocket
by (1.7k points)
WebSocket Server is Microsoft Azure App Service (.Net Core 2.1)
by (1.7k points)
I knew the cause of the problem.
If I use ws: // in the URL, I get a 301 error if the actual server uses wss: //.
If I use wss: // in the URL, Connect is success.
The default WebSocket handles this automatically, but Rebex WebSocket does not seem to handle it automatically.
by (132k points)
Yes, 301 is a redirect response (possibly from ws:// to wss://), which is not supported by Rebex WebSocket yet. We'll add this ASAP and send you a link to an update.
by (15.2k points)
Hello, here you can download a beta build of our WebSocket component that handles HTTP redirects:
https://www.rebex.net/getfile/abc834216f804518b9ac443b8354a6a5/RebexWebSocket-BetaBuild6916-Trial-Binaries.zip
Please note it is a trial version.
by (1.7k points)
I tested your beta version.
The same error occurred in the test, and I sent you an email with a log. Please fix the error.
by (15.2k points)
Hello, thank you for the log. It helped us to fix the error. Please donwload a fixed beta build of the WebSocket component here
https://www.rebex.net/getfile/4dcf2c556a96457d952283f454396838/RebexWebSocket-BetaBuild6920-Trial-Binaries.zip
It is a trial version as the previous one. If you encounter any issue, please send us a log again. Thank you and sorry for the inconvenience.
by (1.7k points)
This beta version works very well.
I hope you'll release it in a short time.
by (140 points)
Thank you so much

1 Answer

0 votes
by (140 points)

Thank you so much

...