forked from zaproxy/zap-extensions
-
Notifications
You must be signed in to change notification settings - Fork 1
AddOnDebugging
thc202 edited this page Jun 12, 2019
·
2 revisions
Roughly, the procedure is:
- Have both zaproxy and zap-extensions open in the IDE
- Copy the add-on to the zaproxy project, using the Gradle task
copyZapAddOn
of the corresponding add-on - Refresh the zaproxy project
- Run ZAP in debug mode
- Put your breakpoint anywhere in the add-on code
- Execute your scenario
- When the breakpoint is reached, you may be prompted to define where the source is located, select zap-extensions project
- That's all.
You just have to not forget to copy the add-on and refresh the project after changing the add-on.
- Introduction
-
2.0 Add-ons
- Add-ons: Release
- Add-ons: Beta
-
Add-ons: Alpha
- Active Scan Rules - alpha
- Access Control Testing
- All In One Notes
- Authentication Statistics
- Browser View
- Bug Tracker
- Code Dx
- Community Scripts
- Custom Payloads
- Custom Report
- DOM XSS Active Scan Rule
- Export Report
- Form Handler
- Groovy Scripting
- HTTPS Info Add-on
- Open API Specification Support
- Passive Scan Rules - alpha
- Replacer
- Revisit
- Server-Sent Events
- Sequence Scanner
- Simple Example
- SOAP Scanner
- SNI Terminator
- Technology Detection
- TLS Debug
- Add-on Development
- Add-on Structure
- Add-on Debugging
- Examples
- Upgrade
- Code Structure
- 1.4 Add-ons
(This is work in progress;)