Saita proxy na abokin ciniki na ASP.NET Core SignalR kafin farawa

Yi daidaita abokin ciniki na ASP.NET Core SignalR ta HttpConnectionOptions domin tattaunawarsa da jigilar da aka zaɓa su sami hanyar da aka nufa.

Kafin fara abokin ciniki na ASP.NET Core SignalR, yi daidaita zaɓuɓɓukan haɗinsa:

var connection = new HubConnectionBuilder()
    .WithUrl("https://events.example/hub", options =>
    {
        options.Proxy = new WebProxy("http://proxy.example:8080");
    })
    .Build();

Wannan ɓangaren yana amfani da sabon abokin ciniki na SignalR da System.Net. Sarrafa connection ta hanyar sake zagayowar rayuwar async na aikace-aikacen; riƙe URL ɗin hub a matsayin manufa. Don gwajin hub na jama'a da aka yarda ba tare da an daidaita takardun shaidar proxy ba, jerin proxy na HTTP yana ba da masu shiga tsakani na HTTP.

Saitin jigilaInda proxy ɗin ke aiki
Halin haɗi na asaliHttpConnectionOptions.Proxy yana zaɓar mai shiga tsakani; jigilar WebSocket ta asali ta .NET 8 ita ma tana ba da shi ga ClientWebSocketOptions
HttpMessageHandlerFactoryYana keɓance sarrafa HTTP, ba haɗin WebSocket ba
Wanda aka bayar WebSocketFactoryyana da halin ƙirƙirarsa kuma dole ne ya yi amfani da hanyar da ake buƙata

Tattaunawa mai nasara ba ta tabbatar da an karɓi ramin WebSocket na baya ba. Idan WebSocketFactory na musamman yana amfani da .NET ClientWebSocket, yi daidaita proxy na wannan socket kafin haɗawa. Karanta binciken jigila na matakin ƙarshe da aka kammala sannan ka duba duk wata hanyar komawa da aka yi da gangan.

Tsofaffin misalan ASP.NET SignalR waɗanda ke Connection.Proxy saitawa na wani ƙarni ne. Tare da HubConnectionBuilder, riƙe proxy ɗin tare da sauran WithUrl zaɓuɓɓukan jigila maimakon daidaita buƙatar HTTP marar alaƙa.

Labarai masu alaƙa