Abstract: A method and system for caching HTTP POST requested content using standard caching rules associated with HTTP GET requests are disclosed. When a POST request is received, it is transformed into a GET request with an identifying tag. The identifying tag includes an index value that is unique to the POST request and is based on the POST request's URL and payload. When the POST request has not been encountered before the POST request's URL and payload is stored in a data store. The client then receives a redirect response including the GET request with the identifying tag that it uses to request the data. When the ensuing GET request with the identifying tag is received it is determined if the requested content has been cached. If so, the cached content is returned to the client. Otherwise, the original POST request is recreated and sent to the origin server to retrieve the content. The returned content is sent to the client and is cached using the GET request with the identifying tag.

Abstract: A method and system for managing the replication and version synchronization of updates to a set of source files on geographically distributed heterogeneous content servers with minimal impact on a network's bandwidth. The configuration of each content server is either manually entered or automatically determined. The current version of the source files are created on at least one source server. A Primary global server stores a copy of the current version of the set of the source files along with the configuration of each content server. The Primary global server generates and distributes a particular version change container and version distribution list to each remotely located Secondary global server. Each Secondary global server employs the version distribution list and the contents of the version change container to identify the current version of each source file necessary to upgrade the set of source files on each local content server.

Abstract: A method and system for managing the replication and version synchronization of updates to a set of source files on geographically distributed heterogeneous content servers with minimal impact on a network's bandwidth. The configuration of each content server is either manually entered or automatically determined. The current version of the source files are created on at least one source server. A Primary global server stores a copy of the current version of the set of the source files along with the configuration of each content server. The Primary global server generates and distributes a particular version change container and version distribution list to each remotely located Secondary global server. Each Secondary global server employs the version distribution list and the contents of the version change container to identify the current version of each source file necessary to upgrade the set of source files on each local content server.