Abstract: A web application firewall (WAF) receives an application request from a router, wherein the application request is directed to a web application, and wherein the web application firewall is associated with the web application. The WAF updates the application request to include a first header, wherein the first header includes a copy of a uniform resource locator of the application request, and updates the uniform resource locator to indicate an address of the web application firewall. The WAF analyzes the application request to determine whether the application request is secure, wherein the analysis is based on a rule, and in response to a determination that the application request is secure, updates the application request to include a second header, wherein the second header includes an encrypted signature.

Abstract: A web application firewall (WAF) receives an application request from a router, wherein the application request is directed to a web application, and wherein the web application firewall is associated with the web application. The WAF updates the application request to include a first header, wherein the first header includes a copy of a uniform resource locator of the application request, and updates the uniform resource locator to indicate an address of the web application firewall. The WAF analyzes the application request to determine whether the application request is secure, wherein the analysis is based on a rule, and in response to a determination that the application request is secure, updates the application request to include a second header, wherein the second header includes an encrypted signature.

Abstract: A test environment as described herein allows for testing webpages prior to deployment to a website. More particularly, a virtual test environment allows a developer to virtually test webpages instantiated from representations of webpages stored in a repository. The webpage representations may be dynamically updated in the repository with changes to the webpages made in the virtual test environment to maintain updated webpage representations in the repository to allow webpages to be tested against updated webpages.

Abstract: A test environment as described herein allows for testing webpages prior to deployment to a website. More particularly, a virtual test environment allows a developer to virtually test webpages instantiated from representations of webpages stored in a repository. In an example of testing, upon a change to a webpage of a website, one or more virtual test environments may be instantiated to test the webpage and associated webpages. In an example of test environment functionality, the test environment may generate templates representing webpages from a base template representing a set of features common to the webpages. Furthermore, a centralized computer may be used to coordinate templates representing webpages by, for example, managing naming. The centralized computer may further track virtual test environments. In a further example of test environment functionality, templates representing webpages may be generated from webpage source code of the webpages.

Abstract: A software package retention system that uses pre-defined rules to retain software packages based on how the packages are used, and not merely based on a package's date/time of creation (age) or type. A retention policy server in the system integrates with the build, deployments, and artifact storage systems of a software supplier/vendor to ensure appropriate retentions are met for audit and regulatory compliance and unneeded artifacts or packages are purged to save storage space and lower operational costs. The server has the capability to monitor software deployments to the customer and to developer test environments, and to make rule-based decisions on when and how to run retention policy clean-up jobs and on what packages. With increasing reliance on frequent build and release of software packages across the software industry, package management post-release using the rule-based retention policy provides an efficient and cost-effective solution for legal compliance with retention requirements.

Abstract: A software package retention system that uses pre-defined rules to retain software packages based on how the packages are used, and not merely based on a package's date/time of creation (age) or type. A retention policy server in the system integrates with the build, deployments, and artifact storage systems of a software supplier/vendor to ensure appropriate retentions are met for audit and regulatory compliance and unneeded artifacts or packages are purged to save storage space and lower operational costs. The server has the capability to monitor software deployments to the customer and to developer test environments, and to make rule-based decisions on when and how to run retention policy clean-up jobs and on what packages. With increasing reliance on frequent build and release of software packages across the software industry, package management post-release using the rule-based retention policy provides an efficient and cost-effective solution for legal compliance with retention requirements.

Abstract: A test environment as described herein allows for testing webpages prior to deployment to a website. More particularly, a virtual test environment allows a developer to virtually test webpages instantiated from representations of webpages stored in a repository. The webpage representations may be dynamically updated in the repository with changes to the webpages made in the virtual test environment to maintain updated webpage representations in the repository to allow webpages to be tested against updated webpages.

Abstract: A test environment as described herein allows for testing webpages prior to deployment to a website. More particularly, a virtual test environment allows a developer to virtually test webpages instantiated from representations of webpages stored in a repository. In an example of testing, upon a change to a webpage of a website, one or more virtual test environments may be instantiated to test the webpage and associated webpages. In an example of test environment functionality, the test environment may generate templates representing webpages from a base template representing a set of features common to the webpages. Furthermore, a centralized computer may be used to coordinate templates representing webpages by, for example, managing naming. The centralized computer may further track virtual test environments. In a further example of test environment functionality, templates representing webpages may be generated from webpage source code of the webpages.