zhangq
zhangq
> Triage: What are the failures you're getting? > Can you share server, client and YARP logs? Yarp logs: [2021-07-21.log](https://github.com/microsoft/reverse-proxy/files/6852122/2021-07-21.log) Client: 1.Success  2.Fail  
> Are sticky sessions enabled? not enabled
> What does the Notify request status translate to? Aborted, failed, etc.? > > ``` > 2021-07-21 09:12:22.9642 [Info] [0] Yarp.ReverseProxy.Forwarder.HttpForwarder+Log.Proxying : Proxying to https://172.30.50.13:5400/Notify?id=llr5GncW9Me-mzNuWzMJFQ&access_token=*** > 2021-07-21 09:12:22.9993 [Info] [0]...
> You need sticky sessions to make SignalR work on multiple servers Maybe I know the reason, is there an IpHash LoadBalancingPolicy?
I use IpHashLoadBalancingPolicy solved this problem.
> Sticky sessions also solves this problem. you should try using it. Let me have a try,thank you!
> Sticky sessions also solves this problem. you should try using it. ```json "SessionAffinity": { "Enabled": true, "Policy": "CustomHeader", "FailurePolicy": "Redistribute", "AffinityKeyName": "Cookie" } ``` I configured it like this,...
目前暂时没打算支持，遇到这种情况，你这边可以先进行分页，然后再处理；