WEB application behaviour.
I ran a scan from the web api which failed due to a disk space issue. It had found a number of issues and displayed them but a report could not be generated.
I fixed the space error and rescaned that application. I stopped the scan after a short time and it had found two issues. I exported a report from this scan but it had access to more issues than those listed on the web front end.
I am the curious about the relationship between issues and reports. In the PostgreSQL db I see a reports table with a report object and a issues table with issues. Is the report object only generated at the end of a scan? What is the relationship between issues and reports?
Is there anyway to recover the corrupted scan perhaps pointing issues to a new scan??
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Tasos Laskos on 12 May, 2017 12:36 PM
The report object is basically the contents of the AFR file, like you'd get at the end of a CLI scan. That object is later used to generate reports in different formats.
If the scan crashes though, for whatever reason, the WebUI won't get a chance to retrieve the AFR report, since that happens at the end of the scan.
Also, unfortunately, there's no way to recover a corrupted scan.
Tasos Laskos closed this discussion on 11 Jun, 2017 10:38 AM.