ZAP did not store scanning session info when unexpected OS restart happened
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
Describe the bug
ZAP did not store scanning session info when unexpected OS restart happened
Steps to reproduce the behavior
Run ZAP and start autoscan
Restart OS (in my case it was Windows 10 update in night)
Run ZAP and select persist the session
open last session and observe empty data
Expected behavior
ZAP should store scanning session info when unexpected OS restart happened
Software versions
ZAP 2.14
Screenshots
big data file is from previous completed scan
Errors from the zap.log file
see attached log file
zap-log.zip
Additional context
No response
Would you like to help fix this issue?
- Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the autoscan flow: start ZAP, restart the operating system unexpectedly, then reopen and persist the last session. Begin by reviewing the attached zap.log and the session-loading behavior; done means scanning session information is retained and visible after reopening the last session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100