zaproxy / zaproxy/zaproxy

Provide curl reproductions for Alerts

Open
#5,733 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
15.8k
Forks
2.6k
Avg merge
13h 16m
Merged PRs (30d)
17

Description

Is your feature request related to a problem? Please describe.
There is an add-on (or two?) which provide access to curl via a context menu, but tbh, I tried installing it and while I think I may have seen it once, I can't get it to appear on demand, and I never managed to get it for the Alerts tab (I think I saw it in the context menu for the History tab).

Describe the solution you'd like
Optionally (not sure how optionally should be implemented), it should be possible to generate HTML reports that include an extra row for each issue that includes a curl command which would produce the problematic output.

Bonus points for including a grep --color -C10 ... command which would highlight the problematic portions of the output.

Describe alternatives you've considered
I tried adding/enabling something which offers a context menu to get curl commands, but:

  1. I can't find it, and
  2. my session appears to be ~150mb, whereas the report for the same session is <150kb.

I'd much rather be able to share a report that was perhaps 300kb that happened to include curl commands to someone so that they could trivially reproduce identified problems and then work to address them.

Additional context
In another life, I used to work in this product space. In my current role, I'm looking at the output from various products, and the lack of an easy way to interpret their complaints is fairly frustrating.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing how the Alerts tab is represented in generated HTML reports, then determine where an optional reproduction row could be added. Done should include reproducible curl commands for each alert in a report, with the optional grep command handled consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.