You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When open fuzzer window, the default view can not add locations, the add button in fuzzer location dialog is disabled. You have to click the combination to display Header and body button, then the add button in fuzzer location dialog will be enabled. For first-time users of Fuzzer, it can be confusing as to why the inability to set a location causes the Fuzzer to be unusable.
The default view, the add button is disabled
Clicked to display header and body button, the add button is enabled
Steps to reproduce the behavior
From the site list, select the HTTP request you want to fuzz test. Right-click and select Attack ⇒ "Send to Fuzzer".
In the fuzzer window, you will see this bug
Expected behavior
expect the add button in fuzzer location dialog is enabled. Or the default view is the combination to display Header and body.
Software versions
Zap version 2.15.0
Screenshots
No response
Errors from the zap.log file
No response
Additional context
No response
Would you like to help fix this issue?
Yes
The text was updated successfully, but these errors were encountered:
Describe the bug
When open fuzzer window, the default view can not add locations, the add button in fuzzer location dialog is disabled. You have to click the combination to display Header and body button, then the add button in fuzzer location dialog will be enabled. For first-time users of Fuzzer, it can be confusing as to why the inability to set a location causes the Fuzzer to be unusable.
The default view, the add button is disabled
Clicked to display header and body button, the add button is enabled
Steps to reproduce the behavior
Expected behavior
expect the add button in fuzzer location dialog is enabled. Or the default view is the combination to display Header and body.
Software versions
Zap version 2.15.0
Screenshots
No response
Errors from the zap.log file
No response
Additional context
No response
Would you like to help fix this issue?
The text was updated successfully, but these errors were encountered: