UWP MessageWebSocket not working when manually set proxy

MangoApps 91

My UWP MessageWebSocket not working behind the proxy when i set proxy manually its through 403 error; Forbidden (403). (Exception from HRESULT: 0x80190193)
When I remove manual proxy then it's able to connect successfully

NEED TO USE ANY OTHER CLASS FOR SOCKET CONNECTION BEHIND PROXY LIKR "StreamSocket" etc

HTTPS calls working well only issue with MessageWebSocket

its there anything need to do in code to connect socket connection behind a proxy server?

7424-tinytake14-04-2020-09-23-22-637224332352333136.png

7402-tinytake14-04-2020-09-23-22-637224332352333136.png

MangoApps 91 Reputation points

2020-04-14T12:52:40.073+00:00

@Richard Zhang-MSFT
Richard Zhang-MSFT 6,936 Reputation points

2020-04-14T23:18:43.913+00:00

Hello, 403 errors are usually caused by reasons such as certificate verification errors or credential errors. Is your message server authenticated? If yes, you can enter your credentials when creating the MessageWebSocket. In your other question, I see that you seem to have noticed this. And you can check the request header changes when the proxy is not set and after the proxy is set to analyze the possible cause of the problem.
MangoApps 91 Reputation points

2020-04-15T04:53:22.283+00:00

No, my server doesn't have any credentials
and if there are any errors in certificate or credential how my "Https" call working and only problem with TCP/Socket
and we are not setting any request header from client its just
URL:- wss://hubnew2.example.com:5223
Port:- 5223
await messageWebSocket.ConnectAsync(new Uri(URL));
Richard Zhang-MSFT 6,936 Reputation points

2020-04-15T05:21:30.29+00:00

Hi, I can't reproduce your problem for the time being, you can try to listen to the MessageWebSocket.ServerCustomValidationRequested event, which applies to wss, here is the relevant documentation. You can check whether the event is triggered.
MangoApps 91 Reputation points

2020-04-16T17:10:42.623+00:00

@Richard Zhang-MSFT issue is solved there was some problem in proxy server.. thanks for your support