Abstract: Requests to a server farm are managed in an application intelligent manner based on server health and client information. A request management (RM) module is configured to make smart routing decisions, based on routing rules that relate the nature of requests to a dynamic topology of a server infrastructure. The RM may use its knowledge of server applications, servers, and clients to deny potentially harmful requests from entering the service, route good requests to the suitable machines, and maintain a history of the decisions and consequences automatic and/or manual optimization.

Abstract: Server health and client information are exchanged through headers for request management. Headers in standardized or proprietary protocol communication between servers and a request management module and/or clients and the request management module may be used to exchange server health and client information. The exchanged server health and/or client information may be employed in throttling, routing, and/or load balancing the incoming requests. Rules specified by the client through the header exchange may also be used for throttling, routing, and/or load balancing decisions.

Abstract: Server health and client information are exchanged through headers for request management. Headers in standardized or proprietary protocol communication between servers and a request management module and/or clients and the request management module may be used to exchange server health and client information. The exchanged server health and/or client information may be employed in throttling, routing, and/or load balancing the incoming requests. Rules specified by the client through the header exchange may also be used for throttling, routing, and/or load balancing decisions.

Abstract: Requests to a server farm are managed in an application intelligent manner based on server health and client information. A request management (RM) module is configured to make smart routing decisions, based on routing rules that relate the nature of requests to a dynamic topology of a server infrastructure. The RM may use its knowledge of server applications, servers, and clients to deny potentially harmful requests from entering the service, route good requests to the suitable machines, and maintain a history of the decisions and consequences automatic and/or manual optimization.

Abstract: Requests to a server farm are managed in an application intelligent manner based on server health and client information. A request management (RM) module is configured to make smart routing decisions, based on routing rules that relate the nature of requests to a dynamic topology of a server infrastructure. The RM may use its knowledge of server applications, servers, and clients to deny potentially harmful requests from entering the service, route good requests to the suitable machines, and maintain a history of the decisions and consequences automatic and/or manual optimization.

Abstract: Web request routers are used to route requests to content within a network. The web request routers run on general purpose computing devices that are configured to receive requests, parse the requests and route the requests to the appropriate destination. The web request routers may be configured to perform different routing methods and operations. For example, the web request routers may route requests based on: a type of network traffic (e.g. user/machine); application specific logic, URL patterns and/or other programmed logic. The web request routers may be configured to route the request based on a determined affinity (e.g. document, Uniform Resource Locator (URL), directory path, site collection) of the request. The web request routers may also be configured to perform QOS operations such as auditing, logging, metering, throttling network traffic, prohibiting network traffic and the like.

Abstract: Web request routers in a cloud management system are used to route requests to content within the networks that are associated with an online service. The web request routers receive requests, parse the requests and forward the requests to the appropriate destination. The web request routers may use application specific logic for routing the requests. For example, the requests may be routed based on a document identifier and/or user information that is included within the received request. A look up table may be used in determining a destination for the request. When a location of content changes within the online service, the look up table may be updated such that the web request routers automatically direct content to the updated location. A user may also specify where their requests are to be routed.