Abstract: A link-modifying web server automatically modifies links in each web page as it is served to a client browser. The web page is parsed for links, and the links are looked up in a link mapping database. A replacement field is read from the database. A link modifier alters the link using the replacement field to point to a different server at one of several content delivery providers. One of several replacement links can be selected from the link mapping database depending on network conditions and user account data. A replacement link to one content delivery provider can be chosen rather than another replacement link to a different content delivery provider when one provider's network is responding more quickly or has a lower cost. A provider monitor continuously checks provider performance at each of the content delivery providers. When one provider's network is slow or fails, the provider monitor instructs a delivery rule processor to choose link replacements at other content delivery providers.

Abstract: A load-balancer assigns incoming requests to servers at a server farm. An atomic operation assigns both un-encrypted clear-text requests and encrypted requests from a client to the same server at the server farm. An encrypted session is started early by the atomic operation, before encryption is required. The atomic operation is initiated by a special, automatically loaded component on a web page. This component is referenced by code requiring that an encrypted session be used to retrieve the component. Keys and certificates are exchanged between a server and the client to establish the encrypted session. The server generates a secure-sockets-layer (SSL) session ID for the encrypted session. The server also generates a server-assignment cookie that identifies the server at the server farm. The server-assignment cookie is encrypted and sent to the client along with the SSL session ID. The Client decrypts the server-assignment cookie and stores it along with the SSL session ID.