web-farm

问题 I was thinking how we can find out which server the page was served from: I'd do so by doing something like put a hidden variable on the page which has the IP or server name from the server it got processed. But what do I do for asp.net ajax requests: those that happen as a partial postback? I'd have to put the hidden variable in the update panel, but what if there are many update panels in the page? I checked out another SO post, but the solution was for iis 7. What is the equivalent for

问题 I was thinking how we can find out which server the page was served from: I'd do so by doing something like put a hidden variable on the page which has the IP or server name from the server it got processed. But what do I do for asp.net ajax requests: those that happen as a partial postback? I'd have to put the hidden variable in the update panel, but what if there are many update panels in the page? I checked out another SO post, but the solution was for iis 7. What is the equivalent for

问题 We are using SignalR in a large scale web application. We have deployed multiple web servers handling signalR connections. We have our own Redis backplane implemented, I have the following question: SignalR makes three calls to the server: 1) negotiate, 2) connect and 3) start. If we have a web farm behind a Load Balancer and these three calls end up going to three different servers, would the state of connections be corrupted on all three servers? What would happen in this scenario? I am not

问题 How does Glimpse persist collected data? Is it all saved in memory? Is there a way to persist the data in a database? I ask this because if I have a website installed on multiple machines (load balancing) can I use glimpse for debugging, or is the data collected from one server not accessible from other servers? 回答1: IPersistenceStore is the interface to implement. Glimpse ships out of the box with an in memory store called ApplicationPersistenceStore, but your implementation could write the

问题 I'm trying to set up forms authentication across multiple servers and subdomains. I have static machine keys set up for each application like so: <system.web> <machineKey validationKey="574...7A7" decryptionKey="2C3...A0D" validation="HMACSHA256" decryption="AES" /> </system.web> ...and my forms authentication is configured the same for each application: <forms loginUrl="/login" timeout="2880" defaultUrl="/" path="/" name=".SHAREDAUTH" domain="domain.com" protection="All" /> I've also tried

问题 Our site uses ADFS for auth. To reduce the cookie payload on every request we're turning IsSessionMode on (see Your fedauth cookies on a diet). The last thing we need to do to get this working in our load balanced environment is to implement a farm ready SecurityTokenCache. The implementation seems pretty straightforward, I'm mainly interested in finding out if there are any gotchas we should consider when dealing with SecurityTokenCacheKey and the TryGetAllEntries and TryRemoveAllEntries

问题 The problem is I have 2 IIS Servers working as Web Farm and currently we don't use Client Affinity or Host Name affinity. I just need to know what is the benefits of using Host Name affinity and when we use this type of affinity between Server and Client. I already have information about Client Affinity I just need to get more information about Host Name Affinity and when to use it. Thank you guys for help in advance. 回答1: Application Request Routing (ARR) provides client and host name

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . Can somebody point me to a resource that explains how to go about having 2+ IIS web server clustered (or Webfarm not sure what its called) ? All I need is something basic, an overview how and where to start. Can't seem to find anything... 回答1: What you're after is called Load Balancing. http://www.microsoft.com

问题 This is a very broad question, but hopefully I can get useful tips. Currently I have an ASP.NET application that runs on a single server. I now need to scale out to accommodate increasing customer loads. So my plan is to: 1) Scale out the ASP.NET and web component onto five servers. 2) Move the database onto a farm. I don't believe I will have an issue with the database, as it's just a single IP address as far as the application is concerned. However, I am now concerns about the ASP.NET and

问题 We have installed .net 4.5 Framework in one of our web servers. Our applications are targeted for .net 4.0 and run off multiple servers behind a load balancer. After the installation we get the following error message for some POST requests error_name=System.ArgumentException error_message=Invalid postback or callback argument. Event validation is enabled using in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments