Methods for managing applications using semantic modeling and tagging and devices thereof
US-2015378721-A1 · Dec 31, 2015 · US
US10331441B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10331441-B2 |
| Application number | US-201715814064-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 15, 2017 |
| Priority date | Dec 22, 2014 |
| Publication date | Jun 25, 2019 |
| Grant date | Jun 25, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure describes a system and method that identifies locations in source code files that are associated with particular Web requests. The system generates a fingerprint for each Web request based at least in part on the parameters of each HTTP request. By fingerprinting the properties of the source code that generates each HTTP request, Web requests that are generated by executing the fingerprinted code can be traced back to specific source code files, and in some cases an exact line of code. In many examples, a webpage or an action on a webpage can be traced back to a line of source code that is associated with the request. This may allow a developer to find a software defect or security vulnerability by tracing Web requests of a running application and then mapping suspect Web requests back to corresponding lines of code.
Opening claim text (preview).
What is claimed is: 1. A system comprising: one or more processors; and memory that stores computer-executable instructions that, if executed, cause the system to implement one or more services, wherein the one or more services: identify a Web service request; determine a first fingerprint for the Web service request; locate, within a source code file, a request instruction, the request instruction having a second fingerprint that matches the first fingerprint of the Web service request; and determine that performance of executable code associated with the request instruction is a source of the Web service request. 2. The system of claim 1 , wherein the one or more services further: generate the second fingerprint based at least in part on a syntax of the request instruction in the source code file; and generate the first fingerprint based at least in part on a function signature of the Web service request. 3. The system of claim 2 , wherein the one or more services further: identify a set of parameters of the Web service request; and determine the function signature of the Web service request based at least in part on the set of parameters. 4. The system of claim 1 , wherein the one or more services further: generate a source code index by storing a textual parameter string as a respective keyword associated with the source code file, the respective keyword usable for matching a search query term to the source code file. 5. The system of claim 4 , wherein the one or more services further: generate metadata associated with the source code file, wherein generating the metadata includes: determining first metadata information corresponding to a software package associated with the source code file, the software package including executable software built at least in part from the source code file; determining second metadata information corresponding to a computing environment, the computing environment including at least one host system running at least one service where the software package is deployed as part of a running instance of the at least one service; and storing the metadata associated with the source code file as part of the source code index. 6. A computer-implemented method comprising: identifying a Web service request; determining a fingerprint for the Web service request; locating, within a source code file, a request instruction, the request instruction having a matching fingerprint that matches the fingerprint of the Web service request; and determining that the performance of executable code associated with the request instruction is a source of the Web service request. 7. The computer-implemented method of claim 6 , further comprising: receiving a second source code file associated with a second application; identifying a second request statement in the second source code file; determining at least one second request parameter in the second source code file, the at least one second request parameter associated with the second request statement; determining whether at least one existing keyword matches the at least one second request parameter; and associating the at least one existing keyword to the second source code file. 8. The computer-implemented method of claim 6 , further comprising: parsing the source code file to locate a match of a respective request statement at a line of code in the source code file, the respective request statement being in accordance with syntax of a programming language used in the source code file. 9. The computer-implemented method of claim 6 , further comprising: analyzing the request instruction located at a line of code in the source code file to identify at least one request parameter that is included as part of the request instruction; and assigning a keyword corresponding to the at least one request parameter, the keyword to be associated with at least the source code file to facilitate searching the source code file. 10. The computer-implemented method of claim 6 , wherein a source code search engine performs search queries on source code documents stored in source code repositories, the source code repositories corresponding to a plurality of applications that are deployed in at least one host system. 11. The computer-implemented method of claim 10 , wherein the search engine further uses metadata associated with one or more source code documents to filter search results indicating respective source code documents. 12. The computer-implemented method of claim 11 , wherein the metadata includes information pertaining to a package, a group of packages, or an environment that includes a deployed application. 13. A non-transitory computer-readable storage medium having stored thereon executable instructions that, as a result of being executed by one or more processors of a computer system, cause the computer system to at least: identify a Web service request; determine a fingerprint for the Web service request; locate, within a source code file, a request instruction, the request instruction having a matching fingerprint that matches the fingerprint of the Web service request; and determine that the performance of executable code associated with the request instruction is a source of the Web service request. 14. The non-transitory computer-readable storage medium of claim 13 , wherein the executable instructions further comprise instructions that, as a result of being executed by the one or more processors, cause the computer system to: receive a second source code document associated with source code for a second application; identify a second request statement in the second source code document; determine at least one second request parameter in the second source code document, the at least one second request parameter associated with the second request statement; determine whether at least one existing keyword matches the at least one second request parameter; and associate the at least one existing keyword to the second source code document. 15. The non-transitory computer-readable storage medium of claim 13 , wherein the executable instructions further comprise instructions that, as a result of being executed by the one or more processors, cause the computer system to: parse the source code file to locate a match of a respective request statement at a line of code in the source code file, the respective request statement being in accordance with syntax of a programming language used in the source code file. 16. The non-transitory computer-readable storage medium of claim 13 , wherein the executable instructions further comprise instructions that, as a result of being executed by the one or more processors, cause the computer system to: analyze the request instruction located at a line of code in the source code file to identify at least one request parameter that is included as part of the request instruction; and assign a keyword corresponding to the at least one request parameter, the keyword to be associated with at least the source code file to facilitate searching the source code file. 17. The non-transitory computer-readable storage medium of claim 13 , wherein a source code search engine performs search queries on source code documents stored in source code repositories, the source code repositories corresponding to a plurality of applications that are deployed in at least one host system. 18. The non-transitory computer-readable storage medium of claim 17 , wherein the search engine further uses metadata associated with one or
Related publications grouped by family.
Answers are generated from the same data shown on this page.