波音游戏-波音娱乐城赌球打不开

Tips on Developing Web Applications for Web Farms

by Wilson Wong

?

The CityU central web servers (www.jvrhmfr.xyz and www6.cityu.edu.hk) are load-balanced web farms, which provide high availability services to the communities. In case any server instance of a web farm is unavailable (due to errors or maintenance), other server instances of the same web farm can still serve requests without service interruptions. 

Session Management
 
When a user visits our central web servers through a web browser, the central load-balancer (according to its internal algorithm) redirects the corresponding HTTP/HTTPS request to one of the server instances. For web applications that require continuous user interactions (for example, asking users to submit data via a web form), users may encounter broken sessions if related HTTP/HTTPS requests of a user session are redirected to other server instances. To  minimise issues of broken sessions, sticky persistent  has been enabled in the load-balancer which ensure all requests of the same user session are redirected to the same server instance. However, should the serving server becomes unavailable, the load-balancer will still redirect subsequent requests of the same user session to another server instance, hence users will still encounter issues of broken sessions.
 
To increase the persistency of .NET web applications, web developers are strongly recommended to make use of static machine keys for session state in web applications requiring user interactions. This would allow the session data of .NET web applications to be decrypted correctly among different server instances in the web farm. Therefore, even the serving server instance, A, becomes unavailable unexpectedly and the subsequent requests are redirected to another server instance, B, the server instance B could still decrypt the session data correctly with the static machine keys and avoid broken sessions.
 
To generate machine keys for your web application:
 
  • Locate and edit the web.config in the application root folder.
  • Add a <machineKey> section under <system.web>.
    <machineKey> section defines a pair of keys, validationKey and decryptionKey, which is used for encrypting, decrypting and validating session data. This pair of keys can be generated by the IIS Manager of your development PC as follows:
     
    • On your development PC, run the Internet Information Services Manager (inetMgr.exe)
    • Double-click “Machine Key” to open the Machine Key feature
      1. Select “AES” under “Decryption method:” and un-check “Automatically generate at runtime” and “Generate a unique key for each application” under “Validation key” and “Decryption key” respectively
      2. Click “Generate Keys” in the “Actions” panel on the right
      3. Copy  the generated “Validation key” and “Decryption key” into the  <machineKey> section under <system.web> in the web.config file as shown below:

                  (For security reasons, please generate different machine key pairs for different web applications.)

A Note for Using Classic ASP

Classic ASP stores session information in web servers, and therefore web applications developed by Classic ASP cannot share session information among server instances. If your web applications require storing data in a session, please consider building your web applications with ASP.NET instead.

 

References 

 

百家乐官网缆法排行榜| 百家乐游戏发展| 百家乐客户端LV| 易胜博棋牌| 请问下百家乐官网去哪个娱乐城玩最好呢| TT百家乐现金网| 永定县| 百家乐英皇娱乐| 沙龙百家乐官网赌场娱乐网规则| 百家乐赢退输进有哪些| 澳门玩大小| 沙龙百家乐娱乐场开户注册| 噢门百家乐玩法| 网上赌百家乐官网被抓应该怎么处理| 线上百家乐技巧| 送现金百家乐官网的玩法技巧和规则| 大发888在线开户| 网上百家乐大赢家| 手机百家乐官网能兑换现金棋牌游戏 | 百家乐作弊知识| 娱乐城百家乐规则| 百家乐官网现场投注平台| 全讯网12580a.com| 百家乐官网网络赌博真假| 太阳城百家乐官网公司| 嘉善县| 保险百家乐官网怎么玩| 百家乐官网蓝盾有赢钱的吗| 百家乐官网赌博网址| 百家乐官网大轮转| 百家乐官网3式打法微笑心法| 浮梁县| 澳门百家乐官网洗码提成查询| 菠菜百家乐娱乐城| 澳门百家乐图形| 百家乐开户导航| 网上百家乐打牌| 百家乐官网站| 威尼斯人娱乐城首存| 百家乐出千的高科技| 大发888信誉|