Abstract: A system receives one or more software artifacts for enabling a software version change requested for a production environment associated with at least one data center location. The system stores the one or more software artifacts in a memory location of a controlled-access production repository. The system receives a first authorization determination of the one or more software artifacts from an author-user account, the author-user account associated with a developer identity that created the one or more software artifacts. The system receives a second authorization determination of the one or more software artifacts from an additional-user account. Based on the first and second authorization determinations, the system determines whether to package the one or more software artifacts into a manifest for transmission to the at least one data center location.

Abstract: A system receives one or more software artifacts for enabling a software version change requested for a production environment associated with at least one data center location. The system stores the one or more software artifacts in a memory location of a controlled-access production repository. The system receives a first authorization determination of the one or more software artifacts from an author-user account, the author-user account associated with a developer identity that created the one or more software artifacts. The system receives a second authorization determination of the one or more software artifacts from an additional-user account. Based on the first and second authorization determinations, the system determines whether to package the one or more software artifacts into a manifest for transmission to the at least one data center location.

Abstract: A system and method for client-side URL rewriting. In one embodiment the method comprises a client sending a request for content to a client proxy, wherein the request for content comprises a first URL. The client proxy may then rewrite the first URL and redirect the request for content to a reverse proxy server. In such an embodiment, the request for content may be sent to the client proxy based on a proxy configuration of the client. In a further aspect of the method above, rewriting the first URL with the client-side URL rewriter may comprise rewriting the request for content to a second URL, and including an indication of the first URL in the rewritten request for content. Furthermore, the first URL may correspond to an intranet server, while the second URL may correspond to the reverse proxy server.