Abstract: A web application may be developed in an environment which has different components than a target environment, so determining component dependencies and identifying which dependencies are met in a given environment can be helpful when deploying the application. Toward that end, test code makes a request that test file(s) be sent from a protected location in the target environment, such as from a randomly-named folder or from another location that is not directly browsable by a user. Received test file(s) and network protocol headers are parsed, and component dependency metadata such as component names and version numbers are extracted. Based on the extracted metadata, information is determined about the target environment's installed component(s). By comparing component dependency(ies) of the program with the identified installed component(s) of the target environment, compatibility of the target environment can then be reported.

Abstract: A web application may be developed in an environment which has different components than a target environment, so determining component dependencies and identifying which dependencies are met in a given environment can be helpful when deploying the application. Toward that end, test code makes a request that test file(s) be sent from a protected location in the target environment, such as from a randomly-named folder or from another location that is not directly browsable by a user. Received test file(s) and network protocol headers are parsed, and component dependency metadata such as component names and version numbers are extracted. Based on the extracted metadata, information is determined about the target environment's installed component(s). By comparing component dependency(ies) of the program with the identified installed component(s) of the target environment, compatibility of the target environment can then be reported.